Windows 10: Windows 10 is stuck on the Windows log during a cold boot

I've recently reset my PC and since then Windows will not start during a cold boot. It gets stuck on the Windows logo screen. I have to press the reset button on the PC for Windows to start.

NOTE: By cold boot I mean starting by PC 1 day after it's been shut down.


I tried Startup repair which fails every time. The odd thing here is the Startup Repair log path, which is not on the Windows drive. I have 2 disks, disk0 and disk1. The Windows drive is on disk1. The Startup repair log file path is on disk0.


Example:

disk0 has drive D

disk1 has drive C which contains the Windows installation

After Startup Repair fails, the error message states the log file path is: D:\Windows\System32\LogFiles\Srt\SrtTrail.txt . The log file is actually on drive C, same path.

I am mentioning this in case it has something to do with my issue.


When I start my PC after about 1 day, it gets stuck on the Windows logo screen, the black one. The loading animation is not displayed and my keyboard and mouse are not active, even though they are before Windows starts to load. As I mentioned, if I press the PC reset button Windows starts normally even if I shut the PC down and start a few minute later.


I would rather not have to press the PC reset button each time more that 1 day passes between boots. Any ideas?

:)

 

Windows 10 Tweaks

Pressing “Windows+Pause Break” (it’s up there next to scroll lock) opens the “System” Window.

Windows 10: In the new version of Windows, Explorer has a section called Quick Access. This includes your frequent folders and recent files. Explorer defaults to opening this page when you open a new window. If you’d rather open the usual This PC, with links to your drives and library folders, follow these steps:

• Open a new Explorer window.
• Click View in the ribbon.
• Click Options.
• Under General, next to “Open File Explorer to:” choose “This PC.”
• Click OK

credit to Lifehacker.

 

Windows 10 upgrade problem, no input accepted

I really hate having to come here and ask for help, but I really am stumped. It hurts my geek pride. I have a PC with fairly modern hardware in it. It has a p8p67 pro in it. I have tried upgrading windows 10 on it twice now. Both times I have had the same result.

After windows finishes upgrading it goes to the log in/set up screen. I can't do anything. No keyboard or mouse input is accepted.

I will list some, or hopefully all, of the troubleshooting steps I have tried:

• Move keyboard and mouse to different USB ports.
• Try different keyboard or mouse.
• Restart computer, repeatedly.
• Google for related issues.
• Update Bios, because why not.
• Create boot media and revert to windows 7.

The windows 10 system restore boot media works fine with keyboard and mouse. All USB ports work in windows 7. I don't know what is wrong. I suspect that windows 10 is lacking a driver of some sort, but since the computer accepts no input I have no way of checking for which driver let alone installing it.

Please help me figure this out. If I have to revert back to windows 7 again, I am not going to get it upgraded to windows 10. Thank you in advanced.

 

Windows 10 Tweaks

As you may already know, Windows 10 (as well as Windows 8) allow you to log in with a valid Microsoft account, instead of creating a local account that only works on your machine. However, you may prefer to keep a local account for privacy reasons. If you do, though, some Windows 10 features—like Cortana—may not work. Despite the default behavior, the Windows 10 Store is not one of them. You can still log in to your Microsoft account for just the Store without switching to a full Microsoft account. The process, however, is not terribly obvious. To do so, follow these steps:

• Launch the Store from your Start menu.
• Click the user icon next to the search box.
• Click “Sign-in” from the menu that appears.
• Choose “Microsoft account” and log in like normal.
• When the “Make it yours” box appears do not enter your password. Instead, click “Sign in to just this app instead.”

from Lifehacker