Powertoys: Manually updated to v0.18.1 and it crashed Explorer.exe

Created on 23 May 2020  路  8Comments  路  Source: microsoft/PowerToys

Night Light got crashed too.

Area-SetuInstall Resolution-Duplicate

Most helpful comment

Same here, it's been doing that for a couple versions now.

All 8 comments

Same here, it's been doing that for a couple versions now.

Just for curiosity, does the crash happen when updating or does it happen during normal use? As far as I'm aware, when you update PowerToys with the MSI file, the explorer would restart (possibly so some of its functions would work,

I'm not part of the dev team, mind you.

Just for curiosity, does the crash happen when updating or does it happen during normal use? As far as I'm aware, when you update PowerToys with the MSI file, the explorer would restart (possibly so some of its functions would work,

I'm not part of the dev team, mind you.

Yes. It happens while updating. But I probably have noticed 1-2 crashes during normal usage in a previous version.

Same here. The update runs its course and when you think it's about to run the new version, it comes to a screeching halt. Feels like a quick restart of explorer.exe is needed in order to run PT, but for some reason it only kills the process, but doesn't restart it.
Also, while I can restart explorer.exe manually via the Task Manager, there is no way to run PT without rebooting Windows first.

This happened going to 0.18 and 0.18.1 for me... with the added bonus that Explorer goes in to an infinite crash loop forever. In fact it is crashing repeatedly while I type this after updating to 0.18.1.

I can't do anything with my PC right now so I will add more info after I reboot.

Pretty amazing, but my event viewer shows 5,646 instances of explorer.exe crashing in the 7 minutes after I started installing the update. Shows the faulting module is 4-5 different DLLs over and over.

I have no idea if these are helpful, but:

Faulting application name: explorer.exe, version: 10.0.19041.264, time stamp: 0x4595555c
Faulting module name: RPCRT4.dll, version: 10.0.19041.1, time stamp: 0x95fb1254
Exception code: 0xc00000fd
Fault offset: 0x00000000000da6e8
Faulting process id: 0x34b0
Faulting application start time: 0x01d6370476acf0c8
Faulting application path: C:WINDOWSexplorer.exe
Faulting module path: C:WINDOWSSystem32RPCRT4.dll
Report Id: 02d5b3a1-35dd-457e-aaa7-c450e7c3a608
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: explorer.exe, version: 10.0.19041.264, time stamp: 0x4595555c
Faulting module name: ntdll.dll, version: 10.0.19041.207, time stamp: 0xcad89ab4
Exception code: 0xc00000fd
Fault offset: 0x0000000000017866
Faulting process id: 0x2df8
Faulting application start time: 0x01d637047524cbff
Faulting application path: C:WINDOWSexplorer.exe
Faulting module path: C:WINDOWSSYSTEM32ntdll.dll
Report Id: cf851889-2f37-4ccb-8860-e07a5230edfa
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: explorer.exe, version: 10.0.19041.264, time stamp: 0x4595555c
Faulting module name: combase.dll, version: 10.0.19041.84, time stamp: 0x6114ea0b
Exception code: 0xc00000fd
Fault offset: 0x00000000000641da
Faulting process id: 0x5a7c
Faulting application start time: 0x01d637046f199416
Faulting application path: C:WINDOWSexplorer.exe
Faulting module path: C:WINDOWSSystem32combase.dll
Report Id: 14e3e629-f4d8-4b06-a3ab-2694faba5432
Faulting package full name:
Faulting package-relative application ID:

Faulting application name: explorer.exe, version: 10.0.19041.264, time stamp: 0x4595555c
Faulting module name: msvcrt.dll, version: 7.0.19041.1, time stamp: 0xa0b0e71d
Exception code: 0xc00000fd
Fault offset: 0x0000000000055f3b
Faulting process id: 0x3b5c
Faulting application start time: 0x01d6370467ad502a
Faulting application path: C:WINDOWSexplorer.exe
Faulting module path: C:WINDOWSSystem32msvcrt.dll
Report Id: 9aeeeeca-d7ec-455a-9599-d5c2be24f963
Faulting package full name:
Faulting package-relative application ID:

Still happening on 0.18.2.

We are working to replace killing Explorer with something less intrusive.
Closing this as duplicate of https://github.com/microsoft/PowerToys/issues/2730
Thanks.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

niels9001 picture niels9001  路  3Comments

Garconis picture Garconis  路  3Comments

CombeeMike picture CombeeMike  路  3Comments

Marrib picture Marrib  路  3Comments

Martin-Hausleitner picture Martin-Hausleitner  路  3Comments