KB3074678 didn't do anything. Still crashing. Does this also mean the Kb3074681 causes my computer to BSOD when using Speccy? Any one using Speccy getting the BSOD?
The module responsible for the crash is shell32.dll, so we'll have to wait until that gets updated to see if the problem is solved. @All: In the meantime, if you want to keep it installed, just don't use right click but the toolbars for commands (like @Nucleus pointed out earlier). (And if someone got WinDbg installed and some spare time, feel free to examine a crash dump and tell us what is going wrong. )
I was dealing with this crap all day today when trying to set up PCs at home. So glad to see this get fixed. EDIT: Spoke too soon. Already had it installed today and it does nothing. EDIT 2: Uninstalled, rebooted, fixed.
Im not sure if I even installed this update or not..if it came out yesterday then yeah I probably installed it, kind of nervous to even check since if I go to updates and I didnt install it it will and might screw up the laptop is there a way for me to check to see if I downloaded this update? Since windows 10 it installs updates automatically the second I click that update button its gonna download it
Yep...the fix to the fix doesn't fix anything. i wonder if bugs like this persisted after July 29...ridiculous really.
I just had the programm-unistall essue. But after I replcaced the shell32.dll-16399 to 16397, everything is all right.
Yes, this is a very good fix! I can vouch that it works. I had installed 10240 in VMWare without any updates what-so-ever. I copied the shell32.dll file from it, put it on the desktop, took ownership of /Windows/System32, and replaced the bad shell32.dll with the one I just got from my VMWare install. Everything is working perfectly now.
Is there a way to replace this file without taking ownership? Every time I took ownership of something in Windows 8.1, I ended up with severe problems.
I don't know. I had 10166 installed in a VHD (not a virtual machine,) so I rebooted to that, and took ownership of system32. No issues.
I see you exaggerating too much. Ok, it's a bug but the settings that crashed can be changed fyi. Simply, right click cause explorer to crash, uninstalling an update or change network settings can be done selecting the option on the toolbar. While microsoft fix it use the menu! It¡s working
Glad to see the problematic updates are already starting. So about this whole forced windows updates thing....