mirror of
https://github.com/massgravel/Microsoft-Activation-Scripts.git
synced 2026-04-26 14:35:49 +03:00
[GH-ISSUE #605] [Suggestions] Some suggestions about your sites #396
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Microsoft-Activation-Scripts#396
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Nvdtn19 on GitHub (Sep 29, 2024).
Original GitHub issue: https://github.com/massgravel/Microsoft-Activation-Scripts/issues/605
1. In here, you're saying "The Powershell method does not work on Windows 7. Use the Method 2 - Traditional instead". However you can still make it work fine in Windows 7 by having an up-to-date system, .NET Framework 4.8 and WMF 5.1 installed.
2. I don't see you provide a XP activation method in here and here, just provide the activation key. But those keys will only help you when it ask for enter the key during windows installation. It does not activate windows when the installation is complete, and you'll need to activate by online (which no longer works on XP) or calling to Microsoft. Probably you know what happens if you don't activate XP for a while. A workaround is using xp_activate32, but there's a thing here is that I couldn't find official site for them but only found on forums, which have this tool reposted. If necessary you could find more info about this tool on the internet.
@MIOGMIOG commented on GitHub (Sep 30, 2024):
This is a duplicate of #139
@Nvdtn19 commented on GitHub (Sep 30, 2024):
I mean, it's still necessary in some other cases, not just for running MAS only. Stock PowerShell in W7 is outdated anyways and it's need to be updated, just like in W8.1+ to execute new commands. Some programs also requires latest .NET Framework to function normally, WMF 5.1 also requires it. Anyways this is my small suggestions, the decision is belong to yours
@Nvdtn19 commented on GitHub (Sep 30, 2024):
I also have another question. Will this actually change the windows edition (I mean by downgrading/upgrading) or it's just visual changes?
