Damn i'm blind =DSide note: If you want to disable all that NVidia telemetry ET call home stuff, take a look here. Explains and show what to un-check. Perfectly safe.
NVIDIA Adds Telemetry to Latest Drivers; Heres How to Disable It (Update) - MajorGeeks
Thank you so much for pointing that out, i totally missed the nVidia telemetry.
Unticked now aswell :)
As with most of the Sysinternals suite everything is done at standard user level unless you opt for admin access
There is an option to run as administrator,and is located in the File menu, try to uncheck the items after clicking this option (it will cause a refresh of Autoruns)
if you ever get an error when in Administrator mode I would back away from that item and do further research (autoruns gives this access within the program Ctrl-M)
Those particular files are part of the 32/64 bit virtualization system so I have left them in place (not sure so stay cautious)
Searched and found following.
From here
https://answers.microsoft.com/en-us/...7-62046f7e198d
Even tho this is for win8 i guess it applies to win10 aswell.
Burt Harris(2) replied on November 24, 2012
A:
Don't be concerned if autoruns reports these files as not found. Just ignore it. These three files are critical to (and invisible to) 32-bit processes running on a 64-bit processor.
For a little fun you can see this by launching both the native and x86 versions of Windows PowerShell, type the following in both. Somewhat surprisingly you'll get different results:
cd $env:windir\system32
dir wow*
Burt Harris
I knew they were related to the system, didn't know what exactly they did so backed away - a lot of users we see here are dealing with issues that might have been avoided - more that once I have seen people post things like "I Didn't recognise the file so I deleted it ... .... and now such and such does not work"
Thanks for reminding me of this, too. Just used it to find several items I hadn't figured out how to access any other way. Great tool!
--Ed--
After many many restarts i have yet to see my chrome startup with windows, so without jinxing myself
( hopefully )
i think the issue was that " Application Restart #1" unticking it + deleting it seem to have worked.
Also unticked those " files not found "
Huge thanks to Barman58 :)
If the issue appears again, i'll come back
if not then consider my problem as Solved :)
Quote
