Start Menu Stays Open When App is Run as Administrator

just noticed this on a fresh install of 2004 yesterday.

I just for a second time upgraded my 2nd desktop from Windows 10 1909 to 2004.

It has an NVIDIA GTX560 GPU. I has the problem also.

dalchina said:

..you remind me of this.. (why would it have to be a Store app?)

Running an SFC should be something so insanely easy you could tell... your typical Windows user how to do it.



1. Go to the Store and download SFCme. (You'll see a cat in a space suit. The Science Fiction Cat. Download that.) Don't worry about the safety of the app because it's in the Windows Store.
2. Open it and push the big red button labeled 'SCAN'. It warns it could take minutes.
3. If it discovers issues, it offers to fix them with a new FIX button (DISM in disguise). What this app doesn't do is spit out a bunch of unintelligible crap out CBS.logs. 4FS. ( <-- That rhymes with DoorDucksLake.)

Any solution found?

I have this issue too.
Windows 1909 , Lenovo P53 (Intel UHD 630 and nVidia Quadro T1000)

On an older Lenovo P50 with win 1909 and Intel+nvidia gfx I never had this.

SFC /SCANNOW finds no errors

xerces8 said:

Any solution found?

I have this issue too.
Windows 1909 , Lenovo P53 (Intel UHD 630 and nVidia Quadro T1000)

On an older Lenovo P50 with win 1909 and Intel+nvidia gfx I never had this.

SFC /SCANNOW finds no errors

I have the latest Nvidia driver: Version: 452.06 WHQL, Release Date: 2020.8.17. I still have the problem. I really don't know if it is a Microsoft Windows or Nvidia problem.

Thinking about it it is not really a problem but at worst an annoyance. To the developers this has to be really low in importance. If it is ever fixed it may not be until next year at the earliest. If it is an Nvidia problem then they may fix it in a driver update. However, if the graphics card affected is using a driver that has not been updated in a long time then there will never be a fix for the problem.

Ztruker said:

I have an Nvidia GeForce GTX 850 and I do not see the problem. I also have UAC set to Never..
I'll try setting it to the default and see what happens.

Edit: Nope, made no difference. Still works correctly.

The problem is nobody knows what is causing the behavior. The only thing in common is that it happens mostly with computers that have Nvidia graphics.

It happens with both my desktops with Nvidia graphics but not with my laptop with AMD graphics. Note UAC is set to Never for all computers.

Desktop 1:
GPU: Nvidia GTX 560
O/S: Windows 10 Pro 2004

Desktop 2:
GPU: Nvidia GTX 1060
O/S: Windows 10 Pro 2004

Laptop:
GPU: AMD Radeon RX Vega 10 & RX 540
O/S: Windows 10 Home 2004

MisterEd said:

The problem is nobody knows what is causing the behavior. The only thing in common is that it happens mostly with computers that have Nvidia graphics.

It happens with both my desktops with Nvidia graphics but not with my laptop with AMD graphics. Note UAC is set to Never for all computers.

Desktop 1:
GPU: Nvidia GTX 560
O/S: Windows 10 Pro 2004

Desktop 2:
GPU: Nvidia GTX 1060
O/S: Windows 10 Pro 2004

Laptop:
GPU: AMD Radeon RX Vega 10 & RX 540
O/S: Windows 10 Home 2004

It's flaky for sure...

Checking again, I see that the UAC 'workaround' ( here ) that worked consistently for me last month before 19041.450 no longer works now.

Oddly the Desktop with a dedicated Nvida Card no longer has the issue while the embedded Intel Graphics laptop still does regardless of UAC levels.

Here they claim this is fixed in the next Windows version 2009. (preview available)