The things to do after installing Windows 11 follow one order: patch it, then customise it, then lock the disk down. A fresh install looks finished on the desktop, but on our test machine the system drive was already encrypted with BitLocker and still had no protection at all, because nobody had signed in with a Microsoft account.
This checklist covers updates from PowerShell, a driver check, winget bulk installs, privacy and telemetry settings, debloating without breaking Windows Update, WSL, restore points and the BitLocker recovery key. We ran every command in October 2026 on a newly cloned Windows 11 24H2 VM built from our lab template, so each output below comes from that machine.
Which Windows 11 version did you just install?
Check the version first, because it decides whether you are still getting security fixes. Microsoft gives Home and Pro 24 months of updates per feature release and Enterprise and Education 36 months, and 24H2 on Home and Pro has already reached its end of updates according to the Windows 11 release information page. If you installed from an old USB stick, you can be fully patched and still out of support.
Open an elevated PowerShell window (right-click Start, then Terminal (Admin)) and read the edition, the release name and the build:
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' | Select-Object DisplayVersion, CurrentBuild, UBR, EditionID | Format-List
Our lab image reported the 24H2 release on build 26100 with update revision 9457, which is the media our template was built from:
DisplayVersion : 24H2
CurrentBuild : 26100
UBR : 9457
EditionID : EnterpriseEval
Compare that line against the release table before you go further. A supported install passes the line for its edition and the build check.
- Home or Pro shows 25H2, 26H2 or 26H1 (the build 28000 branch some new 2026 devices ship with).
- Enterprise or Education shows a release whose 36-month window is still open: 24H2 or newer, or 23H2 until 10 November 2026.
- The build number matches a release that still has a date in the “End of updates” column.
If you are on Home or Pro and the line still reads 24H2, look in Settings > Windows Update first. Microsoft delivers 25H2 to 24H2 machines as a small enablement package (KB5054156) that needs one restart, because both releases share the same code. Our Enterprise Evaluation VM was never offered it, so when Settings shows nothing, download the current ISO and upgrade in place or reinstall. Our guide to creating a bootable Windows USB covers the media, and the diskpart partitioning guide helps when the target disk still carries an old layout you want wiped first.
Should you turn on System Restore and backups?
Yes, and do it now, before the updates, the registry changes and the debloat, because System Restore was off on our clean install and there was nothing to roll back to. Get-ComputerRestorePoint returned nothing and vssadmin list shadowstorage answered “No items found that satisfy the query.”
Turn it on for C: and cap it at 5% of the disk, so shadow copies can’t quietly fill the drive later. Then take a named baseline point that you will recognise in the restore list. Run this block in Windows PowerShell, the default Terminal (Admin) profile, because the restore point cmdlets do not exist in PowerShell 7.
Enable-ComputerRestore -Drive 'C:\'
vssadmin resize shadowstorage /for=C: /on=C: /maxsize=5%
Checkpoint-Computer -Description 'Clean install baseline' -RestorePointType MODIFY_SETTINGS
Get-ComputerRestorePoint
Two restore points showed up, with a “Windows Update” point logged a fraction of a second before ours:
CreationTime Description SequenceNumber EventType RestorePointType
------------ ----------- -------------- --------- ----------------
20261029101741.611577-000 Windows Update 1 100 17
20261029101741.745268-000 Clean install baseline 2 100 12
A second Checkpoint-Computer call straight afterwards created nothing, because Windows allows one restore point per 24 hours from that cmdlet. So take the baseline point first and do the risky changes after it, rather than expecting a fresh point before each step. The 5% cap came out at 3.13 GB on our 64 GB disk.
A restore point is not a backup, since it lives on the same disk. For actual backups, check these before you put real files on the machine:
- The Windows Backup app has your folders, settings and app list syncing to a Microsoft account.
- File History or another tool copies your user folders to a second disk or a NAS.
- A full disk image exists from a third-party imaging tool, since Microsoft lists the old System Image Backup as deprecated.
The image matters most on a dual-boot machine, where a bad bootloader change can cost you both systems. Our Fedora and Windows 11 dual-boot guide shows why we take that image before touching partitions.
How do you install every pending Windows update?
Run Windows Update until it offers nothing, rebooting between rounds, because a fresh install usually needs a cumulative update, a .NET update and a Defender platform update before anything else behaves. Settings > Windows Update > Check for updates does the job, but the PSWindowsUpdate module is faster to repeat and shows exactly what is pending.
PSWindowsUpdate is a community module from the PowerShell Gallery, not a Microsoft one, and a clean install first needs the NuGet provider to pull it. Windows clients default to the Restricted execution policy, which blocks the module’s script and format files from loading, so the first line relaxes the policy for this window only:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass -Force
Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
Install-Module PSWindowsUpdate -Force -Scope AllUsers
Get-WindowsUpdate -MicrosoftUpdate
The scan took 177 seconds on our VM and listed three items: the Malicious Software Removal Tool, the October cumulative update KB5127648 that moves 24H2 to build 26100.9711 (Microsoft has since listed a newer out-of-band 24H2 build, so you may be offered that instead), and a .NET Framework security update. The Size column claimed 90GB for the cumulative update. The download folder peaked at about 6.7 GB during the install, so read that column as a quirk of the module, not as the space you need.
Install everything in one pass, and keep the reboot under your control with -IgnoreReboot.
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
Windows Update’s own automatic run had already installed the removal tool and the .NET update while we worked on other steps. The cumulative update reported “Installed” after 3,295 seconds, close to 55 minutes on a 4 vCPU VM. The reboot that followed took about eight minutes. Plan the first update round for a time you don’t need the machine.
Run the scan again after the reboot, because the first round rarely catches everything. The execution policy change ended with the old window, so run the Set-ExecutionPolicy -Scope Process line again in the new one before Get-WindowsUpdate, and do the same whenever you use the module later. Our second Get-WindowsUpdate took 36 seconds and still found a Defender security intelligence update. Repeat the install and reboot until the scan comes back empty.
Don’t call a bare Get-WURebootStatus from an unattended script. By default it asks whether to reboot, and in our background run it never returned after the install finished, so we had to kill it. The module’s -Silent switch returns only True or False, or you can skip the check and run Restart-Computer when you are ready.
One setting in Settings > Windows Update is worth a decision, the toggle labelled “Get the latest updates as soon as they’re available”. It only changes how fast you receive non-security features and fixes rolled out gradually, and security updates arrive either way, so leave it off on a machine you depend on and turn it on for a test box.
Are any drivers still missing?
Ask Plug and Play for devices with a problem code instead of scrolling Device Manager, because one command answers the question for every device at once:
pnputil /enum-devices /problem
A machine with every driver in place answers with the tool’s header and one message:
Microsoft PnP Utility
No devices were found on the system.
The wording is confusing: it means no device has a problem, not that Windows found no hardware. Any entry that does appear prints its instance ID and a problem code, and that ID is what you search on the vendor site. On our VM the only non-Microsoft drivers were the Red Hat VirtIO and QXL ones, which is expected for a KVM guest; if you run Windows 11 on Proxmox or KVM, the VirtIO drivers guide covers the ISO those come from.
On physical hardware, run three more checks once the device list is clean:
- Settings > Windows Update > Advanced options > Optional updates lists vendor drivers that Windows held back.
- The laptop or motherboard vendor’s support page has a newer chipset, graphics and firmware package than Windows Update.
Get-PnpDevice -PresentOnly | Where-Object Status -ne 'OK'returns nothing.
Graphics is the one driver we would always take from the GPU vendor rather than Windows Update. The copy Windows Update ships is usually older than the one on the vendor’s site, so game and GPU compute fixes reach you later, and the vendor package also brings its control panel. Check Device Manager > Display adapters afterwards to confirm the driver version matches what you downloaded.
How do you bulk install apps with winget?
Use winget import with a JSON list, so the whole app set installs in one unattended run and you can reuse the same file on the next machine. winget ships inside App Installer on Windows 11, so it is already there after setup; our winget guide covers search, upgrade and pinning in more depth.
Refresh the sources first so the package index is current. Then list what the fresh install already wants to upgrade, because the inbox components age from the day the ISO was built.
winget source update
winget upgrade --include-unknown --accept-source-agreements
On first use winget prints the msstore source terms and the note that your two-letter region is sent to the service; the --accept-source-agreements flag accepts them so the command doesn’t stop. Six built-in components were already behind on a system less than an hour old, including App Installer itself, Edge and Windows Terminal:
Name Id Version Available Source
----------------------------------------------------------------------------------------------------------------------------------
App Installer Microsoft.AppInstaller 1.29.289.0 1.29.380 winget
Microsoft Edge Microsoft.Edge 153.0.4234.46 156.0.4314.50 winget
Microsoft OneDrive Microsoft.OneDrive 26.163.0823.0004 26.183.0920.0005 winget
Microsoft Visual C++ v14 Redistributable (x64) - 14.50.35719 Microsoft.VCRedist.2015+.x64 14.50.35719.0 14.51.36247.0 winget
Microsoft Visual C++ v14 Redistributable (x86) - 14.50.35719 Microsoft.VCRedist.2015+.x86 14.50.35719.0 14.51.36247.0 winget
Windows Terminal Microsoft.WindowsTerminal 1.24.11911.0 1.25.2733.0 winget
6 upgrades available.
Run winget upgrade --all if you want those done now. Several of them updated themselves in the background during our run anyway: App Installer moved to 1.29.380 without us asking.
Next, create the package list. An elevated terminal starts in C:\Windows\System32, so move to your home folder before opening a new file in Notepad:
cd $HOME
notepad packages.json
Paste this list and swap the package IDs for the apps you actually use (find any ID with winget search <name>):
{
"$schema": "https://aka.ms/winget-packages.schema.2.0.json",
"Sources": [
{
"SourceDetails": {
"Name": "winget",
"Argument": "https://cdn.winget.microsoft.com/cache",
"Identifier": "Microsoft.Winget.Source_8wekyb3d8bbwe",
"Type": "Microsoft.PreIndexed.Package"
},
"Packages": [
{ "PackageIdentifier": "Git.Git" },
{ "PackageIdentifier": "7zip.7zip" },
{ "PackageIdentifier": "Microsoft.VisualStudioCode" },
{ "PackageIdentifier": "Microsoft.PowerShell" },
{ "PackageIdentifier": "Notepad++.Notepad++" },
{ "PackageIdentifier": "VideoLAN.VLC" },
{ "PackageIdentifier": "Mozilla.Firefox" }
]
}
]
}
Leaving out a Version field means each package installs at its latest release, which is what you want on a new machine. Run the import and accept the agreements up front so it never stops to ask:
winget import -i packages.json --accept-package-agreements --accept-source-agreements
Each package prints the same short block (download progress lines are trimmed here), and the line that matters is “Successfully verified installer hash”, because it confirms the download matches the hash in the manifest:
(1/7) Found Git [Git.Git] Version 2.56.0.3
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
...
Successfully verified installer hash
Starting package install...
Successfully installed
(2/7) Found 7-Zip [7zip.7zip] Version 26.05
...
(7/7) Found Mozilla Firefox (en-US) [Mozilla.Firefox] Version 157.0.1
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://download-installer.cdn.mozilla.net/pub/firefox/releases/157.0.1/win64/en-US/Firefox%20Setup%20157.0.1.exe
Successfully verified installer hash
Starting package install...
Successfully installed
This render of the same run keeps only the lines that matter, one package per block:

All seven packages installed in 792 seconds with exit code 0. That is slow for seven apps, and the process list showed one likely reason, because Edge and OneDrive setup were updating themselves at the same time and the Windows servicing process was busy. Installers that run together compete for the same disk, and MSI packages wait for each other. We would run the import after the first update round has finished, when the machine is otherwise idle.
To capture the finished machine for next time, winget export -o apps.json writes a list of everything winget can match. Our export printed 57 “Installed package is not available from any source” lines for inbox apps such as Paint and Snipping Tool, then still wrote 26 package IDs, including runtimes like the Visual C++ redistributables. Trim the runtimes before reusing the file, since winget pulls them in as dependencies anyway. Teams that prefer Chocolatey can follow our Chocolatey guide instead.
Which privacy and telemetry settings should you change?
Set diagnostic data to Required and switch off the advertising and suggestion features, which removes most of what a new install sends without touching anything Windows Update relies on. Microsoft documents that “diagnostic data off” (value 0) only works on Enterprise, Education and Server, so on Home and Pro the floor is Required (value 1), and setting 0 there behaves like 1.
Most rows mirror a toggle in Settings > Privacy & security or Personalization > Start. The rows under a Policies key (diagnostic data, activity history and web suggestions) are Group Policy values that override the toggles, and the last row is the File Explorer “Hide extensions for known file types” option:
| What it controls | Registry value | Fresh install | Set to |
|---|---|---|---|
| Diagnostic data level (policy) | HKLM …\Policies\Microsoft\Windows\DataCollection AllowTelemetry | not set | 1 (Required) |
| Tailored experiences | HKCU …\CurrentVersion\Privacy TailoredExperiencesWithDiagnosticDataEnabled | 2 | 0 |
| Advertising ID | HKCU …\CurrentVersion\AdvertisingInfo Enabled | 0 | 0 |
| Locally relevant content from your language list | HKCU\Control Panel\International\User Profile HttpAcceptLanguageOptOut | not set | 1 |
| Activity history | HKLM …\Policies\Microsoft\Windows\System PublishUserActivities | not set | 0 |
| Web suggestions in Start search | HKCU …\Policies\Microsoft\Windows\Explorer DisableSearchBoxSuggestions | not set | 1 |
| Tips and app recommendations in Start | HKCU …\Explorer\Advanced Start_IrisRecommendations | not set | 0 |
| Hide file extensions | HKCU …\Explorer\Advanced HideFileExt | 1 | 0 |
The “Fresh install” column is what our VM had after a setup where we declined the optional privacy prompts. Advertising ID was already off because of that choice, while tailored experiences sat at 2 and file extensions were hidden. Apply all eight values from an elevated terminal, then restart Explorer so the Start and search changes load:
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\DataCollection" /v AllowTelemetry /t REG_DWORD /d 1 /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Privacy" /v TailoredExperiencesWithDiagnosticDataEnabled /t REG_DWORD /d 0 /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\AdvertisingInfo" /v Enabled /t REG_DWORD /d 0 /f
reg add "HKCU\Control Panel\International\User Profile" /v HttpAcceptLanguageOptOut /t REG_DWORD /d 1 /f
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\System" /v PublishUserActivities /t REG_DWORD /d 0 /f
reg add "HKCU\Software\Policies\Microsoft\Windows\Explorer" /v DisableSearchBoxSuggestions /t REG_DWORD /d 1 /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced" /v Start_IrisRecommendations /t REG_DWORD /d 0 /f
reg add "HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced" /v HideFileExt /t REG_DWORD /d 0 /f
Stop-Process -Name explorer -Force
Every line answered “The operation completed successfully.” and Explorer restarted on its own within a few seconds. Reading the values back afterwards showed the new numbers for the seven we re-checked (the advertising ID was already 0 and we didn’t re-read it). A value that reads back proves it was written, not that every feature honours it, so check three things before you rely on them:
- Microsoft documents that setting the policy to 1 disables the “Optional diagnostic data” toggle in Settings > Privacy & security > Diagnostics & feedback, so a greyed-out toggle there is expected, not a fault.
- Only the AllowTelemetry, PublishUserActivities and HttpAcceptLanguageOptOut values appear in Microsoft’s privacy documentation.
DisableSearchBoxSuggestionsis a widely used policy value without a page there, and the remaining per-user values are the ones the Settings and File Explorer options write, so recheck all of them after each feature update. - HKCU values apply to the account you ran them in, so repeat those lines for every user who signs in.
We left Windows Update delivery and Defender cloud protection alone on purpose. Microsoft notes that turning diagnostic data fully off also stops Windows Update failure reports, and both of those features exist to keep the machine patched.
How do you debloat Windows 11 without breaking updates?
Remove named consumer apps with the built-in Appx cmdlets and leave every component that installs, updates or protects the system in place. One-click debloat scripts are where people get hurt, since several of them disable services or strip the Store, and that is when Windows Update, winget or Windows Security start failing weeks later.
Keep these packages no matter what a script suggests, because each one does a job you will miss:
Microsoft.DesktopAppInstallerstays, since it is where winget lives.Microsoft.WindowsStoreandMicrosoft.StorePurchaseAppstay, since inbox apps update through them.Microsoft.SecHealthUIstays, since it is the Windows Security app.- The codec and image extensions (HEVC, AV1, WebP, HEIF, Raw) stay, since Photos and browsers use them.
- The
wuauserv,BITSandUsoSvcservices stay enabled.
List what shipped on your build before you pick, because the inbox set changes between releases. Our 24H2 image provisioned 52 packages for new users:
Get-AppxProvisionedPackage -Online | Sort-Object DisplayName | Select-Object DisplayName
This block removes twelve consumer apps for every existing user and from the provisioned image, so new accounts do not get them back. Edit the list to taste before running it in an elevated Windows PowerShell session, since the Appx cmdlets need compatibility mode in PowerShell 7:
$apps = @(
'Clipchamp.Clipchamp'
'Microsoft.BingNews'
'Microsoft.BingWeather'
'Microsoft.GamingApp'
'Microsoft.GetHelp'
'Microsoft.MicrosoftOfficeHub'
'Microsoft.MicrosoftSolitaireCollection'
'Microsoft.PowerAutomateDesktop'
'Microsoft.Todos'
'Microsoft.WindowsFeedbackHub'
'Microsoft.ZuneMusic'
'MSTeams'
)
foreach ($app in $apps) {
Get-AppxPackage -AllUsers -Name $app | Remove-AppxPackage -AllUsers
Get-AppxProvisionedPackage -Online | Where-Object DisplayName -eq $app | Remove-AppxProvisionedPackage -Online | Out-Null
}
The loop took 377 seconds on our VM while Windows Update and Defender were busy in the background. Provisioned packages dropped from 52 to 40 and installed packages across all users from 133 to 121, with none of the twelve left behind. Microsoft.ZuneMusic is the current Media Player despite the old name, so drop it from the list if you play local music files.
Prove nothing broke before you move on, because a debloat that breaks updates usually stays silent until Patch Tuesday:
winget --versionstill prints a version (ours printed v1.29.380).Get-WindowsUpdatestill finds and installs updates.- Windows Security opens and shows Virus & threat protection as active.
We checked the first two on our VM: the 55-minute cumulative update installed after the removal and winget kept working. After the reboot, Solitaire and Clipchamp (the two we re-checked) had not come back, although the Windows Update log listed a Solitaire install entry during the search, so re-run the removal list after big updates. If you run Enterprise or Education on 24H2 or newer, Microsoft also offers a supported route: the “Remove default Microsoft Store packages from the system” policy removes inbox apps at first sign-in and blocks them from coming back, though it does nothing on Home or Pro.
How do you set up WSL 2 on Windows 11?
Install WSL with one command from an elevated terminal, reboot, and then add the distribution you want by name. A clean install doesn’t include WSL, as our VM confirmed:
wsl --status
The answer tells you exactly what to run next:
The Windows Subsystem for Linux is not installed. You can install by running 'wsl.exe --install'.
For more information please visit https://aka.ms/wslinstall
Install WSL itself from an elevated terminal. The --no-launch flag stops it from opening a distribution window straight away, which is how we ran it unattended:
wsl --install --no-launch
On our VM it enabled the Virtual Machine Platform component through DISM, then downloaded the WSL package from Microsoft, and finished in 273 seconds:
...
Installing Windows optional component: VirtualMachinePlatform
The requested operation is successful. Changes will not be effective until the system is rebooted.
The requested operation is successful. Changes will not be effective until the system is rebooted.
Downloading: Windows Subsystem for Linux 3.0.3
Installing: Windows Subsystem for Linux 3.0.3
Windows Subsystem for Linux 3.0.3 has been installed.
Reboot when it asks. The surprise came afterwards, because that run (with --no-launch, from an unattended session) installed WSL but no Linux distribution, although Microsoft documents Ubuntu as the default that wsl --install adds. After the restart, wsl -l -v answered “Windows Subsystem for Linux has no installed distributions.” So check for a distribution before you assume one is there, and install the one you want by name:
wsl --list --online
wsl --install -d Ubuntu-26.04 --no-launch
The online list offered 24 distributions, from Ubuntu 26.04 LTS and Debian to Fedora Linux 44, AlmaLinux 10 and Arch. Ubuntu 26.04 downloaded and installed in 134 seconds and reported “Distribution successfully installed”. Drop --no-launch if you want it to open straight away, since the first interactive start is where you set your Linux username. Confirm it runs on WSL 2:
wsl -l -v
The VERSION column is the one to read, and it must say 2. Straight after a --no-launch install the state reads Stopped:
NAME STATE VERSION
* Ubuntu-26.04 Stopped 2
The first command run inside it took 33 seconds while the distribution started, and the state then changed to Running. Inside the distribution, uname -r returned 6.18.54.1-microsoft-standard-WSL2, the Microsoft-built kernel that WSL 2 runs in a lightweight VM. WSL 2 needs hardware virtualization, and it worked here inside a Proxmox VM with the host CPU type passed through; on a physical PC, enable Intel VT-x or AMD-V in the firmware if the install complains. For RHEL or Fedora instead of Ubuntu, follow our guide to running RHEL and Fedora on WSL.
Is BitLocker actually protecting your drive?
Possibly not, even when the drive reports as encrypted, and this was the most useful finding of the whole run. Windows 11 starts device encryption during setup with a clear key, and only an administrator signing in with a Microsoft account (or a device joined to Entra ID or Active Directory) removes that key and creates the TPM protector. A local-account setup like ours stays in the half-done state.
Check the system drive from an elevated terminal. manage-bde shows the encryption state, the protection state and the key protectors in one output, so you see the whole picture at once.
manage-bde -status C:
Our fresh install reported 100% encrypted with XTS-AES 128, and in the same output “Protection Off” with no key protectors at all:
Volume C: [Windows]
[OS Volume]
Size: 62.71 GB
BitLocker Version: 2.0
Conversion Status: Used Space Only Encrypted
Percentage Encrypted: 100.0%
Encryption Method: XTS-AES 128
Protection Status: Protection Off
Lock Status: Unlocked
Identification Field: Unknown
Key Protectors: None Found
That combination means the data is scrambled but the key sits on the disk in the clear, so anyone who pulls the drive can read it. If you see it, add a TPM protector and a recovery password:
manage-bde -protectors -add C: -TPM
manage-bde -protectors -add C: -RecoveryPassword
The TPM protector binds to PCR 7 and 11, which means Secure Boot state is part of the check, and the second command prints a 48-digit recovery password (masked here):
Key Protectors Added:
TPM:
ID: {82CF904B-78F4-4F51-A981-A591DA78F116}
PCR Validation Profile:
7, 11
(Uses Secure Boot for integrity validation)
Key Protectors Added:
Numerical Password:
ID: {4897F7F3-9753-43AD-A42C-B2AAA7668E90}
Password:
XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX
This is where a fresh install fools people. After adding both protectors, manage-bde -status C: still said “Protection Off”, so a reader who stops at this point has a recovery key for a disk that is still effectively open. The protectors exist but stay suspended until you enable them explicitly.
Copy the 48-digit recovery password into your password manager before you run the next command. Once protection is on, a firmware or Secure Boot change can send the PC to the BitLocker recovery screen, and that password is the only way past it on a local account.
manage-bde -protectors -enable C:
It answers with a single confirmation line:
Key protectors are enabled for volume C:.
Run manage-bde -status C: again, and this time the status flips, with both protectors listed:
Conversion Status: Used Space Only Encrypted
Percentage Encrypted: 100.0%
Encryption Method: XTS-AES 128
Protection Status: Protection On
Lock Status: Unlocked
Identification Field: Unknown
Key Protectors:
TPM
Numerical Password
This render of the session output (status lines only, the protector output is above) puts the whole sequence on one screen, from the unprotected state to “Protection On”:

BitLocker management with manage-bde needs Pro, Enterprise or Education. Home only has device encryption under Settings > Privacy & security > Device encryption, which turns protection on when you sign in with a Microsoft account.
Where should you keep the BitLocker recovery key?
Keep it somewhere you can reach without this PC, because the machine asks for it exactly when Windows won’t boot: after a firmware update, a Secure Boot change or a motherboard swap. When device encryption finishes on its own after a Microsoft account admin signs in, Windows uploads that key to the account, where aka.ms/myrecoverykey shows it from a phone. A protector you add by hand with manage-bde, as we did on a local account, is not uploaded anywhere, so you have to save it yourself.
Print the recovery password and its ID whenever you need it again:
manage-bde -protectors -get C: -Type RecoveryPassword
The ID is what the BitLocker recovery screen shows you, so record it with the password (digits masked here):
Volume C: [Windows]
Key Protectors of Type Numerical Password
Numerical Password:
ID: {4897F7F3-9753-43AD-A42C-B2AAA7668E90}
Password:
XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX-XXXXXX
Store it in at least two of these places:
- Your password manager holds the ID and the 48-digit password as one entry.
- A printed copy sits with your other important papers.
- Your Microsoft account holds a copy, saved through Control Panel > BitLocker Drive Encryption > Back up your recovery key, an option that only appears when you sign in with a Microsoft account.
- A USB stick that never stays in the same bag as the laptop.
Never save it only on the encrypted C: drive, since that is the one place you can’t open when you need it.
Post-install checklist
Work through it in this order, since each step assumes the one before it finished:
- The DisplayVersion is a release that still receives updates for your edition.
- A “Clean install baseline” restore point exists.
Get-WindowsUpdatereturns nothing after the last reboot.pnputil /enum-devices /problemfinds no devices.winget importfinished with every package “Successfully installed”.- The privacy values read back with the numbers from the table.
- Only the apps you named are gone, and winget plus Windows Update still work.
wsl -l -vshows your distribution on version 2.manage-bde -status C:says “Protection On”.- The recovery key ID and password are stored in two places off this PC.
Keep the packages.json file and the registry block in a private Git repo or a synced folder, and the next Windows 11 install takes one import and one paste instead of an afternoon.