MediaCreationTool.bat
MediaCreationTool.bat copied to clipboard
AveYo
Following software is not supported on Windows Server
No a big issue but, on Windows 11 using send to the upgrade process checks for software's that is not supported on Windows Server which I think is your wrapper but is used to install Windows 11 upgrade. Thank you a complaint or issure as I just uninstalled all the stuff related to trying/testing another program. Oracle was the issue by the way.
C:\Program Files\Oracle\VirtualBox
Same thing just happened to me. qemu-kvm.
https://github.com/coofcookie/Windows11Upgrade/issues/35
shows non VM users having the same issue.
Well for what it's worth Microsoft have wrapped up 22H2 ISO in software that calls it Windows Server but it works fine with the tool least in Windows. Muttering about that elsewhere on the net. I assumed they had just stuffed the ISO in another wrapper caller Windows Server. Once running it recognised my Home Windows 11 so I stopped worrying if I was worrying in the first place.
On 9/25/22 06:56, TerryUK wrote:
Well for what it's worth Microsoft have wrapped up 22H2 ISO in software that calls it Windows Server but it works fine with the tool least in Windows. Muttering about that elsewhere on the net. I assumed they had just stuffed the ISO in another wrapper caller Windows Server. Once running it recognised my Home Windows 11 so I stopped worrying if I was worrying in the first place.
— Reply to this email directly, view it on GitHub https://github.com/AveYo/MediaCreationTool.bat/issues/195#issuecomment-1257200561, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGN3RJD73EXV3OQRM3B633WABKZDANCNFSM6AAAAAAQTVMQIA. You are receiving this because you commented.Message ID: @.***>
Mine went all the way through the upgrade and then on the finaly boot told me Windows Server was not supported. THen it rolled me back.
Did you check winver to make sure your updated to 22H2?
oh yes. Defiantly 22H2. No problems.
The internation English ISO which I used. eg. Win11_22H2_EnglishInternational_x64.iso
Ran the CMD file in bypass11
Open using Windows Explorer zip viewer rather than 7ZIP the downloaded "Code" file.
eg. Open with Windows Explorer, go to bypass 11 directory
Click on "Skip_TPM_Check_on_Dynamic_Update.cmd" to run it... didn't need Admin privileges to run since set up as that.
Then click on the ISO and it worked. Did it on two 11 years old machines.
After installation using the normal Windows update install cumulative for August and September.
Perhaps something is in the mutterings on the Windows Server wrapper but was fine for me as per above.
Been using computers since 1972 may be it was my PDP8 bit skills :).
Mine after the final reboot telling me Windows Server was not supported
I reckon it's the packaging of how they ship out the ISO, English International fine in my case. For the normal update where the hardware is compliant which I used on two one year old laptops it was wrapped up in old text.
Wobbly old Microsoft been shipping out wobbly stuff for years 😉.
On 9/26/22 01:55, TerryUK wrote:
I reckon it's the packaging of how they ship out the ISO, English International fine in my case. For the normal update where the hardware is compliant which I used on two one year old laptops it was wrapped up in old text.
Wobbly old Microsoft been shipping out wobbly stuff for years 😉.
— Reply to this email directly, view it on GitHub https://github.com/AveYo/MediaCreationTool.bat/issues/195#issuecomment-1257711591, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGN3RKAQUHOKGJMWVTWM7DWAFQHJANCNFSM6AAAAAAQTVMQIA. You are receiving this because you commented.Message ID: @.***>
I used:
Win11_22H2_English_x64.iso
Suspect that's the US version. You won't be able to keep your files and apps if you switched to the English International.
Certainly I came across mutterings of Windows Server packaging of it when I was researching how to do the update this time round. Think that was on the DLL approach where they take that specific DLL, remove the contents and resave. Somebody was saying "We will have to wait till Microsoft sort it out".
My theory it's in the USA English ISO rather than the English International one that causes issues.... unless it's a virtual machine thing that some have said.
Anybody using the English non international ISO done it at this stage would resolve. ?
The other 22H2 method is this:
https://www.elevenforum.com/t/installing-windows-11-by-removing-appraiserres-dll-file.3879/page-2
& you open the editor on it, take out all what you see on it, resave as a blank DLL. Then run the ISO, apparently. It's in connection with this method, there were mutterings about the Windows Server wrapper on other threads on the net.... anyhow works for me on this project's code on the international English ISO on a standard Windows PC running last year's version of Windows 11 on unsupported hardware that was done last time round on the CoofCookie method.