Hence the question: Why Give PowerToys Admin Access? Why Give PowerToys Admin Access? It warned me that Fancy Zones and other PowerToys tools might not work properly unless I gave PowerToys admin access, too. It popped up when I opened Windows Terminal as Administrator, as per usual practice. I found myself looking at a suggestion from PowerToys on a test PC yesterday. No further updates will be required, when that repair completes. Then, when you repair the image it should work for Home, Pro, Education and Enterprise even if you - as I did - download the Pro-only ISO. This is actually pretty handy because you can use to cobble together an image for the current build number for Windows (10 or 11) including all recent updates and CUs. Any valid Windows 10 ISO works for Windows 10 ditto for Windows 11. Thus, I learned something useful and can pass it on to you, dear reader. I got explicit evidence to the contrary earlier this week with my own eyeballs, on this very PC. I don’t where I got the idea that the version and kind of ISO used for repair had to match the repair target. If you have a 64-bit Windows 10, then you must use a 64-bit ISO or USB.Īgain, there’s nothing here about version, simply that a valid ISO is required.If you have a 32-bit Windows 10, then you must use a 32-bit ISO or USB.Likewise, the TenForums tutorial on this topic simply says ISO file available for Windows 11 or Windows 10. Indeed the MS Answers advice on this technique says only that one mustĭownload the latest. IDKYCDT = “I didn’t know you could do that.” But apparently, you can. Yep: it definitely says the image is Windows 10 Pro. Targeting install.wim from the Sources directory, DISM unambiguously identifies the Windows version as Windows 10 Pro. Yet the filename and download info at UUP Dump clearly identifies the Windows version as Pro:ġ9045.2546.230118-0641.22H2_RELEASE_SVC_PROD3_CLIENTPRO_OEMRET_X64FRE_EN-US.ISO I’m surprised it worked! Why Say: Win10 Enterprise Image Repair Mismatch?Īs you can see in the lead-in Winver graphic, this PC is clearly running Windows 10 Enterprise (2nd text block). Here’s the thing: I used a Windows 10 Pro image for build 19045.2546 (from ) to make those repairs.

It didn’t fix my problem, but it ran to reportedly successful completion. As part of my production PC repairs the other day, I ran an in-place upgrade install.

8gadgetpack 35.0