Windows Explorer won't start on boot - ongoing mystery

Zerkin

Distinguished
May 21, 2013
22
0
18,520
I've been having this issue for several months now, and I'd be so appreciative for any help I can get!

Computer has worked great on Win 8.1 for a long time, one day a few months ago, computer did a regular windows update, and afterwards, I'd always log in to just a black screen. Eventually I figured out that if I ran explorer.exe in administrator mode, I could get the computer to work, just some parts of windows won't work because explorer is running in administrator.

I talked to a microsoft tech help person who worked on my computer remotely for over an hour. He tried installing, uninstalling, and reinstalling every windows update he could find, and eventually told me "it must be a virus", put me on hold for 30 minutes, and then the call dropped.

I've run malware scans numerous times, no hits.

I've disabled all unneeded or unfamiliar start up applications

I've run sfc /scannow, which always is inconclusive (there were corrupted files but couldn't fix it)

I've run system restore and I get some kind of weird error that it couldn't be completed

I've run full registry cleanings

I've installed every windows update that comes my way (not 10 yet)

I've booted in safe mode, and the same thing happens, except the following error message pops up whenever explorer.exe tries to boot,
"The instructionat 0x6c022eee referenced memory at 0xe2ad7138. The memory could not be written"

I really want to get this fixed before installing windows 10, as I don't want to risk anything getting messed up. Though, who knows, maybe installing 10 would fix something. Computer still runs perfectly. No crashes ever, great performance, and I can do everything I used to...just explorer won't run normally.

Any ideas? Thank you so much for reading.
 
Solution
I hadn't done it from an elevated cmd prompt but I just did and got the same message about some corrupted files not being fixed. Here's a screenshot of the log just so you can see what kind of files the errors were found in. They all seem to be Microsoft Unified Telemetry Client ...

http://i.imgur.com/9GfP7G5.jpg

Would running it from a command prompt from the recovery screen do any good? As in before windows has actually started up?

I used malwarebytes. I checked on combofix and it says it doesn't work for Windows 8.1....

Update: Using the info from those logs, I found out that a specific windows update, from right around when my explorer stopped launching, had been known to cause corrupted files. I ran the script listed in...

Zerkin

Distinguished
May 21, 2013
22
0
18,520
I hadn't done it from an elevated cmd prompt but I just did and got the same message about some corrupted files not being fixed. Here's a screenshot of the log just so you can see what kind of files the errors were found in. They all seem to be Microsoft Unified Telemetry Client ...

http://i.imgur.com/9GfP7G5.jpg

Would running it from a command prompt from the recovery screen do any good? As in before windows has actually started up?

I used malwarebytes. I checked on combofix and it says it doesn't work for Windows 8.1....

Update: Using the info from those logs, I found out that a specific windows update, from right around when my explorer stopped launching, had been known to cause corrupted files. I ran the script listed in THIS article and sure enough....scf /scan now comes back clean!

However I restarted and explorer.exe still doesn't boot unless I do it manually as an admin :/ I suppose I could go back and completely uninstall that update.

Update 2 Uninstalled that one update, nothing changed.

Update 3 Well I uninstalled that one update which caused another update which had attempted to install several times, but fail, to be available. I installed it, which then made the windows 10 upgrade window pop up (it had been trying to install since the night of the 28th, but always failed). I installed windows 10, and now everything seem to be working just fine! Problem solved I suppose!
 
Solution

Zerkin

Distinguished
May 21, 2013
22
0
18,520


Haha, hooray! Actually if you hadn't suggested running sfc /scannow again in an elevated cmd prompt, I probably wouldn't have begun looking through the logs for the corrupt files. I had done so many scans that I wasn't even going to bother with that anymore, so thank you!!