activate from Microsoft servers?

i486 said:

Thanks, but I'd rather just use the .vbs script if it came to that

Running .vbs scripts requires that Windows Scripting Host is enabled on your system.

It's a security risk, since .vbs scripts are used frequently as malware launchers.

Start with a Google search for "vbscript security issues" , "vbscript malware".

OldNavyGuy said:

Running .vbs scripts requires that Windows Scripting Host is enabled on your system.

It's a security risk, since .vbs scripts are used frequently as malware launchers.

Start with a Google search for "vbscript security issues" , "vbscript malware".

Right. I thought I found the script from the tutorials here, but actually it was from an official Microsoft guide: https://answers.microsoft.com/en-us/...0-158f8e5f02e3

i486 said:

You can find out what your Product Key is using the tool ShowKeyPlus.

Thanks, but I'd rather just use the .vbs script if it came to that

Actually ShowKeyPlus can do far more than just tell you the installed key. It can show you the keys used in all previous installations tha you have upgraded from.

It can also tell you the key and its type (Home/Pro, OEM/Retail/MAK) embedded in the machine's firmware (if any). You can also type in a key and it will tell you exactly what it is.

It is written and is maintained by Ten Forums member Superfly and has had a thread here on Ten Forums since 2014.

ShowKeyPlus

What @Bree said.

OldNavyGuy said:

To be clear, it's not that there are "malicious scripts" on TenForums, or Microsoft.

It's that Windows Scripting Host needs to enabled for "any" VBScript to run, which makes using VBS a security risk.

Most scripters have moved on to using PowerShell.

Windows Scripting Host is still enabled for Windows 10 by default? It would seem so based on a search.

I've disabled WSH in the registry since Windows 7, and set the file association for .vbs to open with Notepad.

I do it for my clients as well.

slmgr is one I used to use, but there are other ways to do what it does.

Bree said:

You can easily test this by temporarily swapping out its current hard drive, putting in an empty spare, then trying a clean install.

Or just install to an empty partition on the same hard drive.