massgrave/massgrave.dev
massgrave/massgrave.dev
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Merge pull request #36 from ave9858/grammar-review

Browse Source 
Edit edition change docs
This commit is contained in:
WindowsAddict 2025-03-29 12:53:49 +05:30 committed by GitHub
commit 172b822547
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 13 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
docs/change_office_edition.md
View File

@ -38,20 +38,20 @@ C02D8FE6-5242-4DA8-972F-82EE55E00671 - Microsoft2024 VL - Microsoft::LTS
- Learn more about Office update channels here https://learn.microsoft.com/microsoft-365-apps/updates/overview-update-channels
- You can fetch the latest Office build numbers here https://github.com/ItzLevvie/Office16/blob/master/defconfig
- The official method to change the update channel is taken from these URLs
https://techcommunity.microsoft.com/t5/office-365-blog/how-to-manage-office-365-proplus-channels-for-it-pros/ba-p/795813
- The script has the above list in the database and offers to choose only the Officially supported change path.
https://techcommunity.microsoft.com/t5/office-365-blog/how-to-manage-office-365-proplus-channels-for-it-pros/ba-p/795813
- The script has the above list in the database and offers only officially supported upgrades.
### VL (LTSC) channel limitations
(Applicable to 2019/21/24 VL)
Officially, the update channel can not be changed to/from the VL (LTSC) channel to/from any other channel.
So if the Office installation file or installed channel is from the VL (LTSC) channel, then only that channel will appear in the script
also if your update channel is not from the LTSC channel, then the script won't Offer you the option to change the channel to LTSC.
also if your update channel is not from the LTSC channel, then the script won't offer you the option to change the channel to LTSC.
### Windows 7/8/8.1 limitations
Office C2R is officially not supported on Windows [7](https://learn.microsoft.com/microsoft-365-apps/end-of-support/windows-7-support) / [8](https://learn.microsoft.com/microsoft-365-apps/end-of-support/windows-8-support) / [8.1](https://learn.microsoft.com/microsoft-365-apps/end-of-support/windows-81-support) anymore.
The last available build is fixed on certain builds and won't get any updates. VL (LTSC) channels are not supported on these Windows versions so they won't appear in the script.
The last available build is fixed and won't get any updates. VL (LTSC) channels are not supported on these Windows versions so they won't appear in the script.
---

18
docs/change_windows_edition.md
View File

@ -1,16 +1,16 @@
# Change Windows Edition
- You can find this option in the MAS extras section.
- It can change the Windows 7-8-8.1-10-11 and their Server equivalent editions.
- The script incorporates 4 methods for edition changing:
- It can change Windows versions 7 through 11 and the equivalent server editions.
- The script incorporates four methods for edition changing:
- May's DISM Api Method - Used in Windows 10/11 Core to Non-Core edition change
- [slmgr /ipk Method](https://learn.microsoft.com/windows/deployment/upgrade/windows-edition-upgrades#upgrade-using-a-command-line-tool) - Used in Windows 10/11 where edition license files are already there
- [slmgr /ipk Method](https://learn.microsoft.com/windows/deployment/upgrade/windows-edition-upgrades#upgrade-using-a-command-line-tool) - Used for Windows 10/11 virtual editions
- [DISM Method](https://learn.microsoft.com/windows-server/get-started/upgrade-conversion-options) - Used in Server 2016 and later server versions
- [CBS Upgrade Method](https://github.com/asdcorp/Set-WindowsCbsEdition) - Used in Windows versions before 10
- Available editions that can be changed to are shown in the script based on all these 4 options.
- The script is future-proof, which means that it won't need an update upon the release of new Windows / Server editions and can get the required product key from the system itself.
- The script blocks changing to CountrySpecific, ServerRdsh, and to/from CloudEdition editions since it's officially not supported and the user may face issues.
- The script cannot change,
- The script will show editions available via any of the four methods.
- The script is future-proof, which means that it won't need an update upon the release of new editions because it can get the required product key from the system itself.
- The script blocks changing to CountrySpecific, ServerRdsh, and to/from CloudEdition editions since it's not officially supported and the user may face issues.
- The script cannot change
- Non-Core editions to Core editions (For example, Pro > Home isn't available)
- GAC editions to LTSC editions (For example, Enterprise > Enterprise LTSC isn't available)
@ -24,11 +24,11 @@ If you want to manually change the edition instead of using the script, please f
- To view the list of available editions, open the command prompt as admin and enter
`dism /online /english /Get-TargetEditions`
- Get the keys for the desired edition from [here](hwid.md#supported-products)
- Get a key for the desired edition from [here](hwid.md#supported-products)
- If you are upgrading from Home to Pro, you will need to disable the Internet before performing the upgrade.
- Now enter that product key with this command, replace `<product_key>` with the actual key.
`changepk.exe /ProductKey <product_key>`
- In the Home to Pro upgrade, it may show an error, restart the system anyway. (Use the script if it's still not working)
- In a Home to Pro upgrade, it may show an error, restart the system anyway. (Use the script if it's still not working)
- Activate the changed edition with MAS, that's all.
### Windows Server 2016 and Later