Power shell Starting at boot for a second then dissappearing.

Version 20H2 (OS Build 19042.928) And no, it isn't in the startup folder. And it's not even appearing in task manager's startup tab.

dalchina said:

One thing about what is presumably dark mode is you can barely see text in a screenshot.

Here's what I eventually managed to find of yours:


Try a clean boot (Google or see tutorial if unsure how).
Do you still see that pop up?

If so, start re-enabling items disabled until you identify one related to it.

If not, get a copy of Autoruns, free from MS, which lists everything starting from drivers to context menu extensions.
That has a Find function which you could try using.

Ignoring everything by MS, see if you can use that to find a startup related to this.

Note: a cautious person woud create appropriate backups from a System Restore point to a full disk image (routine disk imaging is recommended endlessly here).

If you search for
C:\WINDOWS\System32\WindowsPowershelI\v1.0\powershell.EXE

you will find other reports of this issue.

I tried clean booting, it still appears. so I tried disabling windows services by group and I assume that windows connect now is the culprit.

I've also tried searching for "C:\WINDOWS\System32\WindowsPowershelI\v1.0\powershell.EXE' in autoruns to no avail.

I'm confused

dalchina said:

Thank you for your reply.


Whilst you could try searching the Autoruns list just for
powershell

it seems you have found a relationship to Windows Connect:


You could try uninstalling it..

To note:

disabling it seems to disable wifi connectivity all together

dalchina said:

Again thank you for your reply.

You mentioned disabling Windows services. Whilst you might do that for test purposes, ensure these are reset to their normal state.

Clearly since the app is not even included in 20H2, removing it has nothing to do with Wifi.

Seems you're disabling something you shouldn't - and you're not precise as to what 'it' is here.

Disabling windows connect now seems to cause my wifi to stop working, idk why.

- - - Updated - - -

Never mind, I have stopped it via autoruns by searching for powershell. Thanks!