Persistent crash on latest Windows 11 Pro Insider Preview build
Any attempt to open the app from either the Start menu or the Open button inside the Windows Store results in the following, even after uninstalling and reinstalling:
Access is denied. (Exception from HRESULT: 0x80070005)
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
at CharacterMap.Services.UserCollectionsService.<>c__DisplayClass10_0.<<LoadCollectionsAsync>b__0>d.MoveNext() + 0x2f8
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
at CharacterMap.Services.UserCollectionsService.<LoadCollectionsAsync>d__10.MoveNext() + 0x14c
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() + 0x21
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task) + 0x70
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task) + 0x38
at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task) + 0x17
at System.Runtime.CompilerServices.TaskAwaiter.GetResult() + 0xb
at CharacterMap.ViewModels.MainViewModel.<LoadAsync>d__80.MoveNext() + 0x107
OS Version: 10.0.22567.100 OS Architecture: X64 App Version: 2021.7.4.0 App Culture: en-US
This lead me to believe there's perhaps something misbehaving on that Windows install, as all that happens at this point (as this is before it hits the iteration part of this method), is using the Windows Storage API's to create or open a folder, which has no reason to throw under normal circumstances - and if I can't create a file nothing is going to work. It also shouldn't be getting "Access Denied" as the files are all inside the app's own private storage area. Especially strange if this happens after an uninstall as that folder would be deleted. I'm not sure how I can be any safer in this method without entirely disabling the Collections features if something happens. 🤔
I'll keep investigating it but I can't replicate anything like it on any of my devices (one of which is on the latest insider build). If you have the ability to do so, it would be really helpful if you could pull the code and tell me what line the code is failing on, otherwise I'm low on ideas, sorry! D;
@RogueScholar Any chance I can follow up on this and ask if the latest update from the Store still crashes for you?