[SOLVED] Powershell error popup dialogue box during shutdown

Feb 11, 2022
3
2
15
For the last few weeks I've been seeing a Powershell error popup dialogue box when I shut down my PC. This appears on the blue "shutting down" screen. It lasts anywhere from a fraction of a second to 15 seconds. Using Event Viewer I think it's related to two Dcom Errors (event iD 10010) that happen during shutdown. I've Googled this error and done all the suggested fixes, such as assigning permission, but this error still doesn't go away.

A lot of information I've found suggests that Dcom errors can be ignored, and I would happily do that, if it wasn't for the popup error box (and its annoying "ding").

System specs:
Operating System
Windows 10 Pro 64-bit
CPU
Intel Core i7 10700K @ 3.80GHz
Comet Lake 14nm Technology
RAM
32.0GB Dual-Channel Unknown @ 1596MHz (22-22-22-52)
Motherboard
ASUSTeK COMPUTER INC. PRIME H570-PLUS (LGA1200)
Graphics
FS2333 (1920x1080@60Hz)
Monitor (1920x1080@60Hz)
4095MB NVIDIA GeForce RTX 3060 (NVIDIA)
Storage
1863GB Crucial CT2000P5SSD8 (Unknown (SSD))
7452GB Seagate ST8000DM004-2CX188 (SATA )
7452GB Seagate ST8000DM004-2CX188 (SATA )
Optical Drives
ATA PIONEER BD-RW BDR-212M
Audio
Sound Blaster Play! 3

I'm not sure what other information to supply that would be helpful, so if you could also advise me on that (and how to get the information) that would be appreciated.
 
Solution
  1. right click start button
  2. choose powershell (admin)
  3. copy/paste this command into window:
  4. Repair-WindowsImage -Online -RestoreHealth and press enter
  5. Then type SFC /scannow and press enter
  6. restart PC
First command repairs the files SFC uses to clean files, and SFC fixes system files
SFC = System File Checker. First command runs DISM - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/what-is-dism?view=windows-11

Try turning this off - https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html

now its possible the cause is a start up program, as they are often the last things to close at shutdown
Try a clean boot and see if it changes...

Colif

Win 11 Master
Moderator
  1. right click start button
  2. choose powershell (admin)
  3. copy/paste this command into window:
  4. Repair-WindowsImage -Online -RestoreHealth and press enter
  5. Then type SFC /scannow and press enter
  6. restart PC
First command repairs the files SFC uses to clean files, and SFC fixes system files
SFC = System File Checker. First command runs DISM - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/what-is-dism?view=windows-11

Try turning this off - https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html

now its possible the cause is a start up program, as they are often the last things to close at shutdown
Try a clean boot and see if it changes anything - make sure to read instructions and make sure NOT to disable any microsoft services or windows won't load right - https://support.microsoft.com/en-au/help/929135/how-to-perform-a-clean-boot-in-windows

all it does is stops programs loading with startup, it doesn't remove anything.

if clean boot fixes it, it shows its likely a startup program. You should, over a number of startups. restart the programs you stopped to isolate the one that is to blame.
 
Last edited:
Solution
Feb 11, 2022
3
2
15
  1. right click start button
  2. choose powershell (admin)
  3. copy/paste this command into window:
  4. Repair-WindowsImage -Online -RestoreHealth and press enter
  5. Then type SFC /scannow and press enter
  6. restart PC
First command repairs the files SFC uses to clean files, and SFC fixes system files
SFC = System File Checker. First command runs DISM - https://docs.microsoft.com/en-us/windows-hardware/manufacture/desktop/what-is-dism?view=windows-11

Try turning this off - https://www.tenforums.com/tutorials/4189-turn-off-fast-startup-windows-10-a.html

The first set of commands found no issues, and SFC /scannow reported no integrity violations.
I checked the fast start up settings and found it was already turned off.

now its possible the cause is a start up program, as they are often the last things to close at shutdown
Try a clean boot and see if it changes anything - make sure to read instructions and make sure NOT to disable any microsoft services or windows won't load right - https://support.microsoft.com/en-au/help/929135/how-to-perform-a-clean-boot-in-windows

all it does is stops programs loading with startup, it doesn't remove anything.

if clean boot fixes it, it shows its likely a startup program. You should, over a number of startups. restart the programs you stopped to isolate the one that is to blame.

I'll be trying this later today.

You may be infected. Most likely has nothing to do with a dcom stuff

I don't think there's an infection, but I won't rule it out just yet. Windows Defender reports nothing after a full system scan. Event viewer shows these happening:

  1. The server {A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D} did not register with DCOM within the required timeout.
  2. Application pop-up: powershell.exe - Application Error : The application was unable to start correctly (0xc0000142). Click OK to close the application.
  3. The server {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} did not register with DCOM within the required timeout.

1 and 2 happen at the exact same time. 3 happens 2 seconds later.

Checking the registry seems to indicate that A463FCB9-6B1C-4E0D-A80B-A2CA7999E25D is associated with SmartScreen while 2593F8B9-4EAF-457C-B68A-50F6B8EA6B54 is associated with PerAppRuntimeBroker.
 
D

Deleted member 14196

Guest
It seems like a clean install would’ve solved this alarm time ago and if it doesn’t then you have actual hardware problems
 
Feb 11, 2022
3
2
15
if clean boot fixes it, it shows its likely a startup program. You should, over a number of startups. restart the programs you stopped to isolate the one that is to blame.

It's been a few days since I tried clean booting. I found two possible causes. Uninstalled the one I no longer needed, and reinstalled the one I still use. The powershell popup has gone on the last several shutdowns.

So hopefully, that's the end of it.