RE: KB938828 (probably) start-up headache
EEK oh my - I'm living the nightmare. I thought it was a bug- nice one at
that I couldnt have devised a better POS if i tried.Icons and desktop flash
on and off. I cannot get into control Panel to uninstall, cannot browse the
file directory have been hacking it through Linux and other apps - very
stubborn as its integrated into everything. Can we get the EU to pull
explorer.exe out as well. Reinstall repair with OEM disks does not fix,
shutting down services does not fix. TaskMGR - run command running
explorer.exe creates a nice sine wave as it opens and closes explorer
constantly flashing the desktop icons on and off my computer is now a strobe
light. CLI is working so there is some hope pulling this KB out with out
wipeing it. Wipe 1hour - hack/fix taking forever and who knows.
> Hi there,
> The latest batch of updates really left me in a mess a couple of days ago.
> Upon rebooting, explorer.exe would not run, leaving me with just the
> wallpaper and the ability to use Task Manager. If I tried to run explorer.exe
> from Task Manager, I was told it could not be found or I didn't have the
> permissions. System Restore would not work and I had the same trouble in safe
> mode (System Restore eventually worked in safe mode, but did not solve the
> problem in normal mode).
> After uninstalling the various updates one-by-one, I finally uninstalled the
> last two together as I'd lost hope this was going to work. They were KB938828
> and KB936021, and to my surprise that actually did the trick. I then
> re-installed the known harmless updates, plus KB936021, and rebooted.
> Everything was as it should be, so I thought I'd see what happened if I
> re-installed KB938828. It failed to install, crashing Windows Update and
> leaving me pretty sure this was the culprit.
> I post this more as a slice of info for Microsoft and other users out there
> who may have found themselves in similar trouble and wondered what was going
> on. And I would also be interested to know if other people have experienced
> the same problem. Maybe there was a software conflict involved?