Part of Desktop Blurred After Closing Start Menu

Region of Desktop where Start Menu displays is blurred after Menu closes

Ive been using Start 10 with Win 10x64 pro just fine for years. However Im now experiencing what is best described as blurred desktop rectangle where start 10 menu displays after the menu closes. The menu itself is not corrupted and appears to work fine.

Start Menu and Win 10 are both set to auto update and are on latest version & patches.

Of note is the fact that issuing "start10 unload" immediately fixes the issue. Otherwise there is no way to clear the corruption without logging out or rebooting.

Any ideas why this might be happening?

I would upload a screenshot but it doesnt appear this function is available when posting.

Thx

10,459 views 9 replies
Reply #1 Top

Hello,
Sorry to hear you are having issues. Please post a video of this issue.

Thanks
Basj,
Stardock Community Assistant.

Reply #2 Top

Heres a link to the snapshot of the issue. Again after executing start10 unload, the corruption is instantly cleared

Reply #3 Top

Hello,
This is a new thing? It was not like this before? If yes, what change? New driver update? Version change? Windows update?

Thanks
Basj,
Stardock Community Assistant.

Reply #4 Top

This started occuring yesterday. I havent patched anything or updated anything myself in weeks (including video drivers) except for having to reinstall norton av due to licensing change. Ive never seen anything like this before. Its so exactly sized to the start10 menu and goes away immediately when unloading start10, i dont have any starting point. It never occurs with native windows start menu. Moreover, if have never seen a display driver bug which caused blurring. Ive seen a ton of bluescreens and other issues, but never anything like this.

I have to wonder is this related to a theme? I havent changed my theme since original install 3 yrs ago.

Im not sure where to start. Hard to believe no one has ever run into this

Reply #5 Top

I can't recall any similar report like yours from others. Please try purge and reinstall steps as mentioned here: [link]. Just make sure to redownload the latest version from your account. Reboot after the purged. Reinstall, and Reboot again after the installation. Retest it. Report back here.

Thank you,

Basj,
Stardock Community Assistant

Reply #6 Top

Thanks for your responses. I have unloaded and reloaded the lasted version. I have run sfc/scannow and dism. There are no corrupted files. When I remove start10 or even just start10 unload, the corruption immediately disappears. I am also running nvidia whql certified video driver and the prev build just in case. 

I have uninstalled rebooted, reinstall rebooted. It looks fine until I open open the menu. Im now running 2021H2 Win 10 with no improvement. 

Also I forgot im running fences too, but i dont think this is relevant.

Lastly, I have been chasing a lingering low windows explorer when opening the context menu (right mouse click). 

I have used shexview to see all of them and disabled all of them. Explorer runs much faster. Im going to try start 10 all over again

Any suggestions would be welcomed.

Happy Holidays

Reply #7 Top

Since you mentioned Norton AV, just for test, please try uninstall Norton AV, reboot, retest your issue. Reinstall Norton AV after the test it done. Report back here.

Thank you,

Basj,
Stardock Community Assistant

Reply #8 Top

Hi,

After several days I found it. I have a program loaded that has run for years without issue with start10. I can only assume that the app broke after a recent windows update.

I determined that Actual Multi Monitors is incompatible currently with Start10. AMM will start to consume windows messages that affect redraw and after a while it hangs explorer with the dreaded spinning cursor. Explorer is completely unresponsive. Killing AMM returns everything to normal

If anyone is considering AMM I would suggest installing the trial before purchase and performing work over several hours. This bug doesnt always manifest itself immediately. I usually had to perform daily work for 4-8 hrs before the failure.

Reply #9 Top

Great, thank you for your feedback. :thumbsup:  

Thank you,

Basj,
Stardock Community Assistant