SystemSettings.exe crashes when setting default apps

There's a difference between debugging a dump with Visual Studio and Windbg, the first I've never done and although I don't believe it works properly Windbg showed me much more data.
 
It already is configured properly (how else have I been able to analyze over hundreds of dumps in the past years).
Symbols are downloaded automatically when opening a dump, I opened your dumps a dozen times with no difference.

Getting back to your problem, please try another in-place upgrade.
 
I'll try that as soon as possible, but it could take a bit.

On a side note. I tried an "!analyze -v" in WinDbg on the crash dump using the following symbol path settings:

Code: 
.sympath srv*c:\MyServerSymbols*https://msdl.microsoft.com/download/symbols

At least here, all symbols for all involved Microsoft DLLs were resolved without problems.
 
I did some thinking and remembered that I downloaded all symbol files for Windows 7, 8/8.1 and 10 (up to a certain build) and until now have a symbol folder of ~73GB. Last time I checked it was around 55-60GB which is a while ago, it may very well be that somehow some symbol files have become corrupted. Ironically, I don't have time to do a simple check for corrupted symbol files and replace them if any, even though I'm not employed at the moment.
 
Hi Patrick,

I came across the same exception and offset with build 1803, in my case when trying to use the Task View interface in explorer. When I get an issue like this I normally run a repair install and as expected this fixed the problem.

The issue appeared to be related to the Connected Devices Platform User Service (CDPUserSvc_xxxxx) not functioning correctly. I can now recreate the exception by stopping this service, so I would suggest checking to make sure it's running in the Services snap-in.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top