Black screen after update

[Antman]

Review your event viewer files. There is a reason to how the problem presented. Perhaps we can find it and take corrective measures.

[Antman]

To your knowledge, was the PC configured to boot directly to the desktop after using NETPLWIZ to enter the logon password automatically?

I had a WindX or Win8 install boot to black screen last week. The difference was, I went black screen after user logon. I got past the issue by using the RE cmd prompt to activate the Administrator account. Because this worked, it meant the problem was in the user profile, HKCU, and not in the machine config, HKLM.

I don’t remember what the problem was. I was dissecting a malware infection and probably scrubbed too hard.

[pcpaul]

How do I review events?

[pcpaul]

It boots straight to desktop without any login.

I am now in safe mode on the desktop

[Antman]

How do I review events?

That is a topic worthy of another post. In the meantime, Admin Tools, Event Viewer, navigate to Windows Logs, System
right click, filter current log
Do not be alarmed at the possible large number of errors. Most will have no bearing on your quality of life. It is also possible that we will not find anything that has any bearing on your recent trouble.

You can apply the same filter to Applications.

[ATTACH]578[/ATTACH]

[Antman]

Now would be a good time to create a recovery image. We can play more aggressively.

But for purposes of forum thread management, this case is solved.

[pcpaul]

I hope your right

[pcpaul]

What do I do after doing the logs?

[Antman]

‘After’ is a funny word. Do you see an event error that says “Your problem was caused by X”?
No.
Create a system image. Prove that you can restore it.
Go to Windows Update. Disable any driver updates. I would even consider purging the Update catalog folder in Windows first.
Run Update.
See what happens.

http://ccm.net/faq/2471-how-to-purge-the-windows-update-cache’]http://ccm.net/faq/2471-how-to-purge...s-update-cache

https://support.microsoft.com/en-us/kb/3073930[/URL]

[pcpaul]

Analysing the events log is not something I have experience in.
There’s loads of errors but I don’t know what I’m supposed to be looking for.

[Antman]

^at least create a restore point and prove that you can restore it

[Antman]

Analysing the events log is not something I have experience in.
There’s loads of errors but I don’t know what I’m supposed to be looking for.

I understand. I also said, “That is a topic worthy of another post.”
You will not learn how to read those log entries this year. Or next year.

You could export the log or post screenshots, but what we ultimately discover will take quite a bit of time on task. The immediate problem is resolved. Take precautionary action and run Windows Update.

I also recommend placing a password on your profile. It could serve as an important check point if the same problem occurs. “Does the black screen occur before or after user logon?”

It is possible that you will not encounter the same problem again.

[Antman]

Above, I referenced a KB article for preventing driver downloads. That page is mostly nonsense.

You need this tool from that page:

http://download.microsoft.com/download/F/2/2/F22D5FDB-59CD-4275-8C95-1BE17BF70B21/wushowhide.diagcab

[pcpaul]

I purged the updates and its been checking for new updates since Friday

[Antman]

Assumption:
You created an image before you proceeded.

What does your I/O look like?
Can we look at the SMART data?