Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to download the Workstation version correctly and the setup.exe cannot be launched #363

Open
PLXT opened this issue Jul 17, 2024 · 5 comments

Comments

@PLXT
Copy link

PLXT commented Jul 17, 2024

I try to upgrade my MacBook from Windows 10 to 11, so I follow this guide

Install Windows 11 on a 2015 MacBook Pro

downloading and creating media seems fine, but after selecting the system version, the cmd window just closes and nothing else happenes

19fd25280bb3c11eb0f956930a66098

I have tried all the presets, and the final results were consistently the same. did i miss any steps?:)

Environment:
Device: MacBook Pro (Retina, 13-inch, Early 2015)
CPU: Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz 2.70 GHz
RAM: 8.00 GB
System Version: Windows 10 Pro for Workstations 22H2

@nondetect
Copy link

nondetect commented Jul 17, 2024

Guide from your link is a bit outdated, and that say's at the beginning of article, and provided link to newest version of guide
Officially your device don't meet System Requirements of Windows 11, so to bypass this requirements you can use another script from this author(Skip_TPM_Check_on_Dynamic_Update.cmd)
Another issues what I see on your screenshot is that generated Windows image don't contains your Windows revision (Pro for Workstation), so I recommend you download official iso from Microsoft website

and after applying script mentioned above run installation from iso

@PLXT
Copy link
Author

PLXT commented Jul 17, 2024

Guide from your link is a bit outdated, and that say's at the beginning of article, and provided link to newest version of guide Officially your device don't meet System Requirements of Windows 11, so to bypass this requirements you can use another script from this author(Skip_TPM_Check_on_Dynamic_Update.cmd) Another issues what I see on your screenshot is that generated Windows image don't contains your Windows revision (Pro for Workstation), so I recommend you download official iso from Microsoft website and after applying script mentioned above run installation from iso

:)
Thank you for pointing that out, workstation is indeed not included in the consumer version.

I check the README again, and notice that a step was indeed missing. for workstation upgrade, need rename the script to ProfessionalWorkstation MediaCreationTool.bat

Screenshot 2024-07-17 170219

it looks like already turn to workstation channel, but i dont know why i still get the same image

Screenshot 2024-07-17 172045

Finally, I tried the method you mentioned of manually downloading the ISO, and it worked fine. Now that I have successfully accessed the upgrade page, I will come back to report after the upgrade is successful.

Screenshot 2024-07-17 175011

@PLXT
Copy link
Author

PLXT commented Jul 17, 2024

Anyway, I successfully upgraded Windows using the ISO. The script 'Skip_TPM_Check_on_Dynamic_Update.cmd' was helpful.

However, there are some minor issues with the MCT script's download image functionality, as mentioned earlier. Before the upgrade, I encountered an issue where my system couldn't run any setup.exe files downloaded by the MCT script, even after applying the patch. What might be causing this?

...now my system has been upgraded, so sorry I may not be able to reproduce this

@PLXT PLXT changed the title Not working at MacBook Pro (Retina, 13-inch, Early 2015) from Windows10 upgrade to 11 Unable to download the Workstation version correctly and the setup.exe cannot be launched Jul 17, 2024
@nondetect
Copy link

nondetect commented Jul 17, 2024

However, there are some minor issues with the MCT script's download image functionality, as mentioned earlier. Before the upgrade, I encountered an issue where my system couldn't run any setup.exe files downloaded by the MCT script, even after applying the patch. What might be causing this?

The script can manually handle all types of Windows revisions. However, problems seem to arise only during the "automated" process in certain situations or with specific revisions. This may be due to changes Microsoft has made in the way it delivers revision packages, which have been altered several times not long ago, and the script has not been updated for quite some time.

@LightYagami28
Copy link

Hi @PLXT you have resolved?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants