I'm leaning more towards the GPU as being a cause, but don't have enough stats to confirm one way or another. Neither I nor my client have Kodi installed, and as a result I'm leaning away from any type of Microsoft "App" being the cause unless a common app could be found that is installed on all problematic installs. Thanks opera, I do recall reading that thread and pretty sure it's where I came to the conclusion that claims Microsoft addressed this problem were garbage and bogus. Interestingly enough all things like xbox and other UWP things, I uninstall using CCleaner Have you read this thread? Read from post 15 and also page 3. Ran a DISM /resorehealth command on my own box and that made no difference either, so it's not likely to be a corrupt system file causing this.Įdited by achzone, 17 March 2019 - 05:39 PM. Running a chkdsk and sfc /scannow showed no issues on either install. I normally create my new folders and files using other means so didn't even notice that I had the same problem until trying to find a solution for my client! Having now experienced it myself, I can see how frustrating it would be if you frequently use the New context menu by right clicking. Hang in there Dorki - we'll get to the bottom of it eventually. There are also claims Microsoft was aware of the problem in Windows 10 earlier builds and that a fix was released - those claims appear to be garbage going by my own research so far. There appears to be a ton of people with the same issue going all the way back to Windows XP - all without a confirmed solution. Removing a host of other Context menu items made zero difference as well - so I've now put them back. It's handy that I've got 24/7 unattended access to my clients machine, so have two boxes to try fixes on.ĥ. On my machine, it's an AMD, on my client's machine, it's an Nvidia - removing those entries from the context menu made zero difference. Found a host of suggestions on the web related to the Graphics Card context menu entry being the cause of the problem. Made no difference to how long it took for the New context menu to open.Ĥ.
I reduced the New context menu down to only contain New > Folder and nothing else. The suggested fix at makes zero difference to the problem, on my machine, or on my clients machine. I have the same build of Windows 10 as my client and Dorki - Version 1809 (OS Build 17763.379)ģ.
No idea when it started unfortunately, but I'm determined to figure out why it's happening now :-) All other context menus appear to work fine and open instantly.Ģ. Tried it on my own machine and it takes nearly two seconds to open on mine too. Just didn't realize it because I rarely use the Right-Click > New context menu. Ok, I've been working on this problem and can now confirm the following:ġ.
0 kommentar(er)
