Those sort of thing always make me nervous however because it's not easy for the average user to tell if its running any sort of malicious scripts in the process. This one seems to be safe and I'm going to give it a try to see what happens.
still works as well which would be even better because thats local and easier to verify its integrity. that being said I think these are both valid suggestions if they work and I'm going to give them a try.
Yes, before running anything, you need to analyze the source. Still, I trust it: it works well, and as the Italian website indicates, you just need to check the linked .cmd file via the URL shortening to see exactly what it does. This should be done before downloading it with curl and before executing it as a .cmd file. The no-oobe solution also has the advantage of allowing the bypass of the entire OOBE phase.
Those sort of thing always make me nervous however because it's not easy for the average user to tell if its running any sort of malicious scripts in the process. This one seems to be safe and I'm going to give it a try to see what happens.
The article also suggests that
"reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OOBE /v BypassNRO /t REG_DWORD /d 1"
still works as well which would be even better because thats local and easier to verify its integrity. that being said I think these are both valid suggestions if they work and I'm going to give them a try.