Various unfixed issues with Windows 10 since June 2020.

things still not fixed in Windows 10 since I installed Windows 10 Pro June 2020..

• upon updating my Nvidia display driver install, the start-menu becomes non-responsive. (MS claimed to have fixed it lol). (killing the START menu process forces it to restart as a workaround.. or restarting the PC)
• Power & Sleep settings, screen settings do not work, screen does not go on standby
• various other issue I have been having..

I am currently running Windows 10 Pro (v21H1)(19043.1320)

the START-MENU issue is a bug Microsoft says they fixed in build 19041.572
from Microsoft via feedback hub 11 months ago:

thanks for taking the time to report this. We've investigated your issue, and have included a fix with Build 19569, as well as Build 19041.572. If you've experienced this issue, please make sure to check that your PC is up to date with the latest version of Windows.

it happens every single time I update my Nvidia display drivers.. but only on my desktop..
it seem to update to v496.49 today on my laptop with Nvidia RTX 3060 6GB and AMD Ryzen 5800H (includes a AMD Radeon graphics in the CPU so the screen didn't blink so maybe thats why it didn't happen on my laptop...


and the Screen timeout settings don't work for me either... currently set to 20 minutes...
it does not go on to standby when 20 minutes passes... worked fine on Windows 7 as far as I can remember..


feel free to ask questions or give advice..

Hello again Melchior ,
Please confirm your BIOS and all drivers are up to date from mobo or PC manufacturer's website.

Run sfc and dism to make sure not Windows system issues are found: Run SFC Command in Windows 10

I would run the following which will disable hibernation and Windows Fast Startup - they could be causing sleep issue: from admin powershell run "powercfg /h off" . If you use and need to turn hibernation back on in the future, you can run "powercfg /h on" after you're done testing.

Please confirm Turn On or Off Fast Startup in Windows 10 is off too.

Since you said you already tried rolling back the video driver without success, I won't suggest that.

steve108 said:

Hello again Melchior ,
Please confirm your BIOS and all drivers are up to date from mobo or PC manufacturer's website.

Run sfc and dism to make sure not Windows system issues are found: Run SFC Command in Windows 10

I would run the following which will disable hibernation and Windows Fast Startup - they could be causing sleep issue: from admin powershell run "powercfg /h off" . If you use and need to turn hibernation back on in the future, you can run "powercfg /h on" after you're done testing.

Please confirm Turn On or Off Fast Startup in Windows 10 is off too.

Since you said you already tried rolling back the video driver without success, I won't suggest that.

lol of course all my drivers and BIOS are up to date as I am a PC enthusiast etc..
I frequent various websites like this one for updates...

I have not bothered with sfc or dism... kinda scared to run them and it muck up my PC... I haven't been having any other issues...
other then a rare bug with the BIOS where the system will randomly lockup... it now only occurs once a week maybe..


While I don't use SLEEP-mode, fast startup works great for me... haven't had any issues there either..


like I said its a Windows bug and/or a bug with the Nvidia display driver installer...

You're not a PC enthusiast if sfc and dism scare you.

Do you make image backups? Backup and Restore with Macrium Reflect

There's a thread where many people said if you have a SSD boot drive, fast startup does not buy you anything perceptible - give it a try for yourself. I don't use it either.

Melchior said:

I have not bothered with sfc or dism... kinda scared to run them and it muck up my PC... I haven't been having any other issues...

The main reason why people run sfc /scannow (and dism /Online /Cleanup-Image /Restorehealth if it found some errors that it cannot fix) from an elevated command prompt is because they're kinda scared not to run them and not running them muck up their PC. Running them fixes corrupt system files that you may not always notice were corrupted... we shouldn't have to deal with this stuff because a well engineered OS should remember to keep its own system files intact... Microsoft got nicknamed 'Mickeysoft' because the reliability of their software products is a real joke, and continues to be that... pertinently.

hdmi said:

The main reason why people run sfc /scannow (and dism /Online /Cleanup-Image /Restorehealth if it found some errors that it cannot fix) from an elevated command prompt is because they're kinda scared not to run them and not running them muck up their PC. Running them fixes corrupt system files that you may not always notice were corrupted... we shouldn't have to deal with this stuff because a well engineered OS should remember to keep its own system files intact... Microsoft got nicknamed 'Mickeysoft' because the reliability of their software products is a real joke, and continues to be that... pertinently.

ok understood..


My boot device is a: 1TB Samsung Evo 970 (NVMe)(SSD)
the fast startup was very fast as I had shut my PC down while I took a nap to a concern over a downed Comcast coaxial-cable...
something snagged that cable outside and ripped it from pole right outside my front door..

- - - Updated - - -

a sfc /scannow test only revealed two broken files

Windows PowerShell ISE.lnk
Windows PowerShell ISE (x86).lnk

and the source files also corrupt lol cannot repair...
strange since the files work fine and I haven't changed them...

and some folder permission issue that were trivial.... lol

That's the 'thing'... it has the ability to get itself corrupted in some way that getting corrupted requires no user action of any kind, but getting it to repair itself next typically does. Rather marvellous, isn't it?

Melchior,
Did you run dism with the /RestoreHealth option as the sfc tutorial suggests to do? You would then run sfc again and see if the problem is resolved. Notice that the tutorial says to run sfc three with fast startup turned off, rebooting between each run.

If test with fast startup disabled, you probably won't find any perceptible difference in performance.