New
#1000
Before the update my image backups were 24GB. After the update they're 18GB. Did Windows go on a diet? :)
Before the update my image backups were 24GB. After the update they're 18GB. Did Windows go on a diet? :)
Dirk, I wanted to ask you about your registry thing a bit more specifically. You said you pretty much trumped the issues with an edit of certain DCOM Errors entries? Do you think this may help fix the right click menu "New" wait issue?
I can't imagine the two things are related in any way. That said i had forgotten about this being a possible 1809 bug so i just tried it. I don't have any delay. That could just be because i got lucky this time or it could be down to any number of other Regedits or tweaks i apply, some of which are actually related to Context Menus. I tend to apply them all at once though, and as i wasn't testing this particular issue it's impossible to say if one of them 'fixed' it, or whether it simply wasn't an issue in the first place.
Something worth mulling over. I upgraded rather than clean installed. While i was on 1803 i had already used ShellExView to resolve an issue by disabling a bunch of shell extensions. As this tool has been touted before as a way to fix problems such as this delay, it's very likely that i preemptively fixed it. More likely that anyway, than the Regedits, which mostly just remove items from the Context Menus.
I remember reading before about Nvidia shell extensions causing a delay in context menus, long before 1809 was released:
How to Fix a Slow Windows 10 Desktop Right-Click (Context) Menu
Sonething related to Delays in general and ShellExView:
Fixing shell extension problems with ShellExView
If a shell extension is causing the problem i bet a lot of trial and error testing using that utility would get to the bottom if it.
Removed a lot of stuff they think you don't need any more.
Windows 10, version 1809 - Features that have been removed | Microsoft Docs
Microsoft Details Deprecated and Removed Features in Windows 10 Version 1809 - Thurrott.com
Also removed many printer drivers & maybe other drivers, as well.
I think there is a thread on this forum detailing it.
...and here it is...
Features being removed or deprecated in Windows 10 version 1809 - Windows 10 Forums
Revert back again to win 10 1803.
I don't know why by installing 1809 I can't shutdown, sleep or even restart PC. everything else works without problem.
no matter a fresh start or upgrading by windows update.
I also have a surface it doesn't has problem with 1809.
Even though you didn't give enough info about the issues you are facing, a good starting point would be to do a routine check:
-Run in command prompt with admin privilege:
sfc /scannow to see if you have any integrity violations. If you do, try to run the whole gamut of DISM command lines, like:
Dism.exe /online /Cleanup-Image /scanhealth
Dism.exe /online /Cleanup-Image /restorehealth
Dism.exe /Online /Cleanup-Image /AnalyzeComponentStore
if the result for the latter command line is "Yes", you will have to run also:
dism.exe /Online /Cleanup-Image /StartComponentCleanup
Lastly, you can also try to update the driver for your display adapter in Device Manager. To have a better idea of what causing you these issues, you can also go for a system diagnostic report:
How to Generate System Diagnostics Report in Windows 10:
Generate System Diagnostics Report in Windows 10
At least, that will give you a good indication of what might be causing your troubles. Take note that you won't be able to upgrade to 1809 normally until the time you fix the underlying issue. I hope that the aforementioned steps can either fix your problem or put you on the right track. Cheers!![]()
Thanks for your reply
1) about this command I'd done that: sfc /scannow nothing found.
2) display driver was latest
3) System report I'll do that maybe it indicates the problem reason.
I hope that this problem not related to any hardware issue.
I would also look on Asus's site for drivers related to Power Mgmt.
Just went through a similar issue with a Lenovo. Once the correct device drivers were installed and Lenovo's PM driver it started acting normal. Check the appropriate Asus drivers are installed. May even need to update BIOS