Current Status of Windows 10 October 2018 Update version 1809

mahdian57 said:

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.

To update the driver, you have to check with the manufacturer's site as already mentioned by @Caledon Ken. Don't expect Windows Updates to find it for you. More often than not, it will always tell you: "Windows has determined that the latest driver is already installed...bla...bla", which is not true in most cases.

To another point, if it were related to a hardware issue, it would probably do the same thing when you rolled back to 1803. So, this shouldn't worry you. I think you have a good chance of finding the main reason of your problems with a system diagnostics report.

thanks a lot my friends around the world!
currently I'm on 1803. I'll try your suggestions when updating to 1809. (some of them wasn't successful to indicate the main reason such as turning off fast startup and etc. )

mahdian57 said:

thanks a lot my friends around the world!
currently I'm on 1803. I'll try your suggestions when updating to 1809. (some of them wasn't successful to indicate the main reason such as turning off fast startup and etc. )

On a last note, here is a quick tutorial to find the latest driver for your PC using the hardware ID:

https://www.groovypost.com/tips/quic...s-hardware-id/

One word of caution though, never use a third-party app to update the driver, but always the manufacturer's site. And lastly, if nothing is working, you can always try a repair install (in-place upgrade) or as a last resort a clean install. The former will keep your data files and your already installed apps, while with the latter you are on a clean slate, meaning nothing is kept, and you definitely ought to do a system image backup before going for it.

How to Do a Repair Install of Windows 10 with an In-place Upgrade

Repair Install Windows 10 with an In-place Upgrade

How to clean install Windows 10:

Clean Install Windows 10

You can also backup your drivers , when everything is ok .
In case of troubles its easy to recover.........!!

There are many tools , made for this job .
Im using Driver Booster and Yamicsoft , they both make excellent backups , no headache anymore..............

Dirk Gently said:

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.

Downloaded the utility but I can't find which one controls the NEW fly out menu. I don't even think there is anything in there to help correct the delay behavior. I'm not a techy kind of person when it comes to this deep sort of stuff. I tried disabling the NVIDIA and there was ONE other entry that sort of looked like it pointed to handling the NEW fly out menu... rebooted but it was still there. The NVIDIA menu on the right click was gone though but it was obviously not causing the ultra slow delay on the NEW fly out menu ongoing issue I'm having.

There was a registry fix that I downloaded from one of the threads here but when I tried to merge it with my registry it wouldn't go in.... See below if I can get it uploaded here and maybe you or someone can look it over and correct what ever needs correcting to make it usable?

RAMWolff said:

Downloaded the utility but I can't find which one controls the NEW fly out menu. I don't even think there is anything in there to help correct the delay behavior.

The easiest way to troubleshoot with ShellExView is to use the option to hide all Windows entries from the list. Then disable what's left and test to see if the delay is gone. If it is, great. Re-enable each entry one by one, testing each time, until you find the one causing the issue and leave that one disabled.

Of course that only helps if it's a third-party extension causing the problem. Judging by how common this issue is it's probably a Windows component that's broken.

What happens when you try to use the .reg? Do you get a warning of some sort? You would have to be running as Administrator to use it.

You might want to wait for MS to fix it. For the time being, if there's something you use the 'New' menu for a lot, you might want to see if there's a keyboard shortcut or alternate method to achieve the same end.