Mmmm. We have our friends at Microsoft to thank for this. See discussion here and the many scathing comments.
http://blogs.technet.com/b/the_micro...-updates-.aspx
I suspect that you too have installed the early December 2014 updates from MS.
I had deliberately held off updating my system with the December updates having learnt from experience in the past. I prefer to wait and see if I hear of any problems. As I mentioned my system was working fine when I tested your files. I had planned last night to install the updates which I did overnight. Imagine my horror when I checked this morning and found my system was now exhibiting the same problem you encounter. Not only that but the system restore point I had carefully created (again from long experience) would not restore when I tried to restore my system to the pre December updates.
I googled around and found the link I mention above, among many others in a similar vein.
This site mentions a subsequent MS fix, KB 3025036. When I googled this I found the following Microsoft support item
http://support.microsoft.com/kb/3025036
On this page you'll see a 'Fixit' button that you can click to fix it automatically, (or it can apparently be done manually by deleting all .exd files which is a bit of a faff and not something I looked forward to doing). When I clicked the Fixit button it downloads a small program which you can run and after it finishes (it only takes a few seconds) it seems to have fixed the problem. I'm still holding my breath and am totally cheesed off with Microsoft for subjecting everyone to this problem, many of whom will not have an IT support service to easily fix it.
Try this and let me know. You'll obviously need to apply this on every PC on which you've updated the December updates.
Bookmarks