Discord: unknown: (no content)
Discord: reverieviee: Hey! Thanks for testing all of that. I checked WinHance, and it uses essentially the same Windows command to mount the ISO and retrieve its drive letter.
That explains why both programs fail. Windows mounts the ISO, but Get-Volume does not return its drive letter. This does not appear to be protection on the ISO, especially since a fresh download behaves the same way on multiple test environments.
Since DISM and SFC found corruption but repairing it didn’t resolve this, the next thing I’d suggest is:
Settings > System > Recovery > Fix problems using Windows Update > Reinstall now
This reinstalls the current version of Windows while preserving your apps, files, and settings. There’s no pressure to do this just for our testing, but it’s the last reasonable Windows repair step I can think of.
Microsoft has more information about it here.
Discord: .kiltedfrog: I can test this no problem, but might be in a few days.
I had a thought though. I was once having trouble using System Restore and creating restore points. I found out that it was a mod in Windhawk that was holding it back (specifically Resource Redirect). I’ll try disabling Windhawk and see if that solves the issue. Fingers crossed!
Discord: reverieviee: Best of luck
Discord: .kiltedfrog: Windhawk wasn’t the problem.
I did the Repair method through Windows Update like you suggested, and that seems to have fixed the problem. My thanks for your efforts!
Discord: reverieviee: Oh nice! Let me document that in the GitHub issue. Thanks for the update and glad it worked