# SX1337 Win10 Deploy

PowerShell GUI bootstrap for rebuilding a Windows 10 22H2 Pro machine after reinstalling.

## Files

- `bootstrap.ps1`: tiny entry script. Put this at the root of your setup subdomain.
- `sxsetup.ps1`: local WinForms GUI runner.
- `manifest.json`: task list, installer URLs, silent arguments, detection rules, and homepage fallbacks.
- `version.json`: tool and manifest version metadata.

## Server layout

Upload all files in this folder to the root of your setup subdomain:

```text
https://setup.sx1337.top/bootstrap.ps1
https://setup.sx1337.top/sxsetup.ps1
https://setup.sx1337.top/manifest.json
https://setup.sx1337.top/version.json
```

Run this command from an elevated PowerShell window:

```powershell
powershell -NoProfile -ExecutionPolicy Bypass -Command "[Net.ServicePointManager]::SecurityProtocol=[Net.SecurityProtocolType]::Tls12;$u='https://setup.sx1337.top/bootstrap.ps1';$p=Join-Path $env:TEMP 'sx1337-bootstrap.ps1';Invoke-WebRequest -UseBasicParsing $u -OutFile $p;powershell -NoProfile -ExecutionPolicy Bypass -File $p -BaseUrl 'https://setup.sx1337.top'"
```

If a fresh Windows install cannot complete the HTTPS handshake, use this HTTP fallback:

```powershell
powershell -NoProfile -ExecutionPolicy Bypass -Command "$u='http://setup.sx1337.top/bootstrap.ps1';$p=Join-Path $env:TEMP 'sx1337-bootstrap.ps1';Invoke-WebRequest -UseBasicParsing $u -OutFile $p;powershell -NoProfile -ExecutionPolicy Bypass -File $p -BaseUrl 'http://setup.sx1337.top'"
```

## Notes

- The tool does not integrate KMS activation scripts. It only detects Windows activation status.
- Server bandwidth stays low because installers are downloaded from vendor URLs, not from your server.
- Some installers may change their direct URLs or silent switches. Update `manifest.json` when that happens.
- Logs are written to the current user's desktop.