It’s 9:12 AM. You’ve got a “simple” Windows issue: broken updates, weird boot times, VPN client won’t load, and your laptop has become an expensive space heater. Someone says, “Just reinstall Windows, you can keep your apps.” That sentence is either the start of a clean recovery… or the start of a long afternoon explaining to Finance why the accounting suite needs “a quick reauthorization” (again).
This piece is about the difference between what Windows can actually do versus what vendors and hopeful forum posts imply. We’ll cover the options, how they fail, and how to prove—using commands and outputs—whether you’re about to keep your apps or about to erase your week.
The terms vendors blur on purpose
When people say “reinstall Windows,” they might mean any of four different operations. Only one reliably keeps apps in the way most humans mean “apps.” The rest either keep files only, keep some Microsoft Store apps, or keep nothing but your regrets.
1) Clean install (wipe and install)
This is the honest option. You boot from install media, delete partitions or format the OS volume, and install fresh. You can preserve a Windows.old folder if you install onto the same partition without formatting, but that saves user data and some system state—not working applications.
2) Reset this PC
Windows Settings offers “Reset this PC” with choices like “Keep my files” or “Remove everything.” The “Keep my files” path keeps user profiles and some settings but removes installed desktop applications. It may keep some built-in apps. It is not “keep apps,” no matter how politely a dialog box phrases it.
3) In-place upgrade repair install (the actual “keep apps” move)
This is the one that can preserve installed Win32 applications and most settings: run Windows Setup from within Windows (not booting from USB), choose to keep personal files and apps, and let Setup lay down a new OS while migrating the existing install.
If you need one rule: if you boot from USB, “keep apps” is usually off the table. Setup needs the running OS context to perform a full migration of applications and registry state.
4) Image restore / bare-metal restore
This keeps apps because it keeps everything. But it’s not a “reinstall,” it’s time travel. You restore a full-disk image from earlier and accept that anything installed or changed since the image is gone.
Joke #1: A “reinstall that keeps apps” is like “diet cake.” Sometimes it exists, but you should still read the label.
What “keep apps” really means: the only paths that work
Here’s the practical truth: for traditional desktop apps (Win32), the only Microsoft-supported method that resembles “reinstall Windows and keep apps” is the in-place upgrade repair install. Everything else is either a reset (apps removed) or a clean install (apps removed, files maybe recoverable).
The in-place upgrade repair install: what it does
- Replaces Windows system files with a fresh copy from install media or Windows Update sources.
- Rebuilds the component store (WinSxS) and re-registers many system components.
- Migrates installed applications, drivers, and settings as best as it can.
- Creates rollback artifacts and logs (like
C:\$WINDOWS.~BT, Panther logs).
What it does not promise
- It won’t keep broken apps working if they depended on corrupted system components, deprecated drivers, or old runtimes that get replaced.
- It won’t keep licensing state for every product. Some licensing survives; some products treat it as a new machine.
- It won’t preserve security software integrations reliably. Endpoint protection, VPNs, and low-level drivers are frequent casualties.
Non-negotiable prerequisites if you want “keep apps” to be real
- You must be able to boot into Windows and run
setup.exefrom inside the OS. - You need sufficient free disk space on the OS volume (plan for tens of GB).
- You need the right media: same edition, compatible language, and typically same or newer build.
- Disk and file system health must be good enough to survive large-scale file operations.
Fast diagnosis playbook
When someone asks, “Can I reinstall Windows and keep apps?” don’t answer yet. First, diagnose what you’re dealing with. The bottleneck is usually one of: disk health, system corruption, update stack damage, insufficient space, or third-party drivers.
First: establish whether a repair install is even possible
- Can you log in? If no, you’re already drifting toward reset/restore/clean install.
- Is the OS volume healthy? If the disk is failing, stop. Image it, back it up, replace it, then recover.
- Is BitLocker enabled? If yes, make sure you have recovery keys and understand what will prompt for them.
Second: identify the actual failure mode
- Update failures? Check DISM/SFC and the servicing stack logs.
- Boot slowness? Inspect event logs for disk resets, driver timeouts, and service hangs.
- App crashes? Look for missing runtimes, corrupted user profiles, or incompatible drivers.
Third: choose the least destructive fix that meets the SLA
- Try servicing repairs (DISM, SFC) if you can. They’re reversible and cheap.
- Do an in-place upgrade if core components are broken but you need apps.
- Clean install when integrity or security is suspect, or the system is too far gone.
Paraphrased idea from Werner Vogels (AWS): reliability comes from automation and design, not heroics at 2 AM. Treat Windows recovery the same way—repeatable steps beat improvisation.
Hands-on tasks: commands, outputs, decisions (12+)
Below are practical tasks you can run before committing to a reinstall. Yes, these are Windows commands, but I’m providing them in shell-style blocks as requested. Run them in an elevated Command Prompt or PowerShell where appropriate. Each task includes: command, example output, what it means, and what decision you make.
Task 1: Confirm Windows version and build (compatibility check)
cr0x@server:~$ cmd /c ver
Microsoft Windows [Version 10.0.19045.4046]
What it means: Build 19045 indicates Windows 10 22H2. Your install media must be compatible (same major version, ideally same or newer build).
Decision: If your media is older (e.g., 19041), expect higher risk of downgrade behavior or disabled “keep apps” options. Obtain matching media.
Task 2: Check edition (Home/Pro/Enterprise mismatch kills “keep apps”)
cr0x@server:~$ cmd /c "dism /online /Get-CurrentEdition"
Deployment Image Servicing and Management tool
Version: 10.0.19041.3636
Current Edition : Professional
The operation completed successfully.
What it means: This system is Windows Pro. Repair install media should be Windows Pro (or multi-edition media that includes it).
Decision: If you only have Enterprise media but the device is Pro, don’t “just try it.” Get the right ISO.
Task 3: Measure free space (repair installs are space-hungry)
cr0x@server:~$ cmd /c "wmic logicaldisk where DeviceID='C:' get Size,FreeSpace"
FreeSpace Size
41234583552 255998611456
What it means: About 41 GB free on C:. That’s usually enough for in-place upgrade plus rollback files, depending on the OS and apps.
Decision: If free space is under ~25–30 GB, plan cleanup or temporary storage expansion before attempting repair install.
Task 4: Check BitLocker status (avoid surprise recovery prompts)
cr0x@server:~$ cmd /c "manage-bde -status c:"
BitLocker Drive Encryption: Configuration Tool version 10.0.19041
Volume C: [OS]
Conversion Status: Fully Encrypted
Percentage Encrypted: 100.0%
Protection Status: Protection On
Lock Status: Unlocked
What it means: OS drive is encrypted. Setup can work, but you need recovery keys accessible and should consider suspending protection during the upgrade.
Decision: If you can’t retrieve recovery keys, stop and fix that first. Otherwise you’re one firmware update away from a bad day.
Task 5: Quick disk health signal (SMART via WMIC is limited but useful)
cr0x@server:~$ cmd /c "wmic diskdrive get model,status"
Model Status
NVMe Samsung SSD 980 PRO 1TB OK
What it means: WMIC reports OK. This is not a full SMART analysis, but if it says “Pred Fail,” believe it.
Decision: If disk status is not OK, don’t attempt an in-place upgrade. Backup/image first; replace storage.
Task 6: File system check scheduling (catch corruption early)
cr0x@server:~$ cmd /c "chkdsk c: /scan"
The type of the file system is NTFS.
Stage 1: Examining basic file system structure ...
Windows has scanned the file system and found no problems.
No further action is required.
What it means: NTFS metadata looks consistent.
Decision: If errors are found, repair them (chkdsk /f, likely requiring reboot) before attempting any OS migration.
Task 7: System file integrity check (SFC)
cr0x@server:~$ cmd /c "sfc /scannow"
Beginning system scan. This process will take some time.
Windows Resource Protection found corrupt files and successfully repaired them.
What it means: Corruption existed but was repaired. Often this resolves update failures without a reinstall.
Decision: Reboot and retest the original issue. If corruption can’t be fixed, move to DISM and possibly in-place upgrade.
Task 8: Repair component store health (DISM)
cr0x@server:~$ cmd /c "dism /online /cleanup-image /scanhealth"
No component store corruption detected.
The operation completed successfully.
What it means: The WinSxS component store looks healthy.
Decision: If corruption is detected and /restorehealth fails, an in-place upgrade is often the fastest safe repair that keeps apps.
Task 9: Check whether Windows can find recovery environment (Reset depends on it)
cr0x@server:~$ cmd /c "reagentc /info"
Windows Recovery Environment (Windows RE) and system reset configuration
Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
What it means: WinRE is enabled. Reset options are viable if you accept app removal.
Decision: If WinRE is disabled or missing, “Reset this PC” may fail. Don’t discover this mid-crisis.
Task 10: Inspect recent bugchecks and disk errors (Event Log triage)
cr0x@server:~$ cmd /c "wevtutil qe System /q:\"*[System[(EventID=7 or EventID=51 or EventID=55 or EventID=1001)]]\" /c:5 /f:text"
Event[0]:
Log Name: System
Source: Microsoft-Windows-WER-SystemErrorReporting
Event ID: 1001
Description: The computer has rebooted from a bugcheck...
What it means: There are recent critical errors. Event ID 7/51/55 are often disk or NTFS problems. 1001 indicates crashes.
Decision: If disk-related events appear, prioritize storage health over OS reinstall. Fix hardware first.
Task 11: List installed apps the way enterprise tools see them (inventory before surgery)
cr0x@server:~$ powershell -NoProfile -Command "Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName,DisplayVersion | Sort-Object DisplayName | Select-Object -First 5"
DisplayName DisplayVersion
7-Zip 23.01 (x64 edition) 23.01
Google Chrome 121.0.6167.141
Microsoft 365 Apps for enterprise 16.0.17231.20182
Notepad++ (64-bit x64) 8.6.4
Zoom Workplace 6.0.2
What it means: This is your baseline. Not all apps register here (some portable apps don’t), but most enterprise software does.
Decision: Export this list before changes. If the user later claims “everything is gone,” you have receipts.
Task 12: Capture drivers (3rd-party drivers often break after repair)
cr0x@server:~$ cmd /c "pnputil /enum-drivers | findstr /i \"Published Name Provider\" | more"
Published Name : oem12.inf
Driver package provider : Intel
Published Name : oem45.inf
Driver package provider : Realtek
What it means: You can see third-party driver packages. Network and storage drivers matter most for survival.
Decision: If the system relies on a vendor-specific storage driver (e.g., RAID), confirm you have a reinstall path before touching Windows.
Task 13: Confirm activation channel (helps predict post-reinstall activation behavior)
cr0x@server:~$ cmd /c "slmgr /dli"
Name: Windows(R), Professional edition
Description: Windows(R) Operating System, RETAIL channel
Partial Product Key: XXXX
License Status: Licensed
What it means: Retail channel is usually tied to a Microsoft account or key, not an enterprise KMS setup.
Decision: If activation is via KMS/MAK, confirm corporate activation works after major repairs. Otherwise you’ll “fix” Windows into an unlicensed state.
Task 14: Validate system reserved/recovery partitions exist (boot safety)
cr0x@server:~$ cmd /c "diskpart /s %TEMP%\dp.txt"
Microsoft DiskPart version 10.0.19041.3636
DISKPART> list vol
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C OS NTFS Partition 238 GB Healthy Boot
Volume 1 EFI FAT32 Partition 100 MB Healthy System
Volume 2 Recovery NTFS Partition 990 MB Healthy Hidden
What it means: EFI and Recovery partitions are present. That’s a good sign for sane boot behavior.
Decision: If EFI/Recovery is missing or broken, prioritize fixing boot infrastructure; reinstall plans change.
Task 15: See whether Windows Setup is likely to allow “keep apps” (practical check)
cr0x@server:~$ cmd /c "setuperr.exe"
'setuperr.exe' is not recognized as an internal or external command,
operable program or batch file.
What it means: You don’t have Setup logs because you haven’t run setup yet. After a failed in-place upgrade attempt, logs live under Panther directories.
Decision: If an in-place attempt fails, you will pull logs from C:\$WINDOWS.~BT\Sources\Panther and stop guessing.
Three corporate mini-stories (what went wrong, what saved us)
Mini-story 1: The incident caused by a wrong assumption (the “keep apps” myth)
A mid-sized company had a fleet of Windows 10 laptops used by a sales team. A handful of devices were stuck failing cumulative updates, and someone proposed a quick fix: “Reset this PC, keep my files. That’s basically a reinstall that keeps apps.” It sounded plausible. The UI was friendly. The calendar was not.
The reset worked. The machines booted cleanly. Users could open spreadsheets again. Then the real outage arrived: the CRM client plugin, the meeting room booking add-in, and a line-of-business VPN client were gone. The users’ documents were intact, so the operation was declared a success for about six minutes.
Reinstalling the missing software wasn’t just “download and click Next.” Some installers required admin approval, some needed offline license files, and one depended on a legacy runtime that had to be staged in a specific order. Meanwhile, endpoints drifted into non-compliant states because the management agent itself had been removed by the reset. Devices stopped checking in. That triggered security tooling alarms and blocked network access for some users.
The wrong assumption wasn’t that Reset is bad. Reset is fine when you accept app loss. The wrong assumption was treating “keep my files” like “keep my environment.” Those are different promises with very different blast radii.
The remediation was boring: inventory apps first, confirm licensing, and use an in-place upgrade repair install where “keep apps” actually means something. The lesson stuck because it cost real productivity and a lot of ticket updates.
Mini-story 2: The optimization that backfired (space saving meets Windows Setup)
A different org tried to reduce storage usage on developer workstations. Someone rolled out aggressive disk cleanup policies: large temp folders purged, delivery optimization caches limited, and user profile redirections tightened. The machine images looked lean. The dashboards looked green. Everyone congratulated themselves quietly.
Then a repair install wave hit—several devices needed in-place upgrades to fix broken servicing stacks. Setup started and failed with vague errors. A pattern emerged: machines with the strictest cleanup settings had the highest failure rate. The OS volume didn’t have enough working room for Setup to stage files, create rollback data, and perform migration steps.
What made it painful was the “almost works” nature. Setup would run for a while, then roll back. Users lost hours. IT lost credibility. And because the rollback restored the previous broken state, the outcome was a perfect circle of wasted time.
The fix wasn’t exotic: temporarily relax cleanup policies, ensure sufficient free space, and allocate a predictable buffer. Windows Setup is not a minimalist. It wants staging area, logs, and rollbacks. Deny it and it gets petty.
That “optimization” did reduce average disk usage. It also increased incident frequency. In production terms, it lowered cost per node and raised cost per outage—an awful trade if you care about your weekends.
Mini-story 3: The boring but correct practice that saved the day (imaging and keys)
An enterprise had a strict practice for “OS repair events”: before any major Windows repair or reinstall, technicians had to capture (1) BitLocker recovery keys, (2) a basic app inventory, and (3) a bare-metal image of the OS volume for the high-risk machines. People grumbled. It felt slow. It felt bureaucratic.
One week, a batch of laptops began exhibiting intermittent NVMe timeouts. Not full failure—just enough to corrupt files occasionally and cause strange behavior. A few were scheduled for in-place upgrade repairs because the symptoms looked like update corruption. The process started on a Friday (because of course it did).
During the upgrade, two devices hit storage errors and became unbootable. Because imaging had been done first, recovery was straightforward: replace the drive, restore the image to get user state back, then perform a controlled migration to a fresh OS install. Recovery keys were already in the ticket, so nobody had to chase users who were in transit.
That practice didn’t prevent failure. It turned failure into a routine. That’s the point. You don’t need heroics; you need a runbook and the boring discipline to follow it.
Interesting facts and historical context (so you know why Windows behaves like this)
- “Repair install” used to be a boot-from-CD concept. Older Windows versions had repair modes from installation media, but modern “keep apps” behavior is tied to in-OS migration logic.
- Windows side-by-side components (WinSxS) exist to support servicing at scale. It’s why Windows can apply updates to a huge matrix of system states—until the store corrupts, then everything gets weird.
- Windows 10’s “Windows as a service” era changed upgrades. Feature updates became frequent in-place upgrades, so Microsoft invested heavily in migration tooling that also powers repair installs.
- Reset this PC evolved for consumer recovery, not enterprise continuity. It’s designed to get a home machine working quickly, not preserve complex app stacks and corporate agents.
- Activation became more resilient with digital licenses. Many systems re-activate after reinstall based on hardware ID, but enterprise licensing and certain software vendors still behave like it’s 2009.
- UEFI and GPT standardized boot layouts. Modern Windows relies on EFI partitions and recovery partitions; missing or damaged ones cause “mystery” boot failures after reinstall attempts.
- Driver signing and kernel security raised the bar. Old VPN and AV drivers are more likely to break during OS refresh operations because they sit deep in the stack.
- Microsoft Store apps are packaged differently. They can be re-registered or reinstalled in bulk; traditional Win32 apps are mostly “stateful snowflakes.”
- Windows Setup writes detailed logs. Many admins don’t read them, then act surprised when guesswork fails. The logs are there; use them.
Failure modes: how “keep apps” breaks in real life
If you want to keep apps, you need to understand what threatens that outcome. These are the usual suspects.
Edition, language, and build mismatches
Windows Setup offers the “Keep personal files and apps” option only when it determines a supported migration path. If your media is wrong—different edition, different language, too old, not matching architecture—Setup quietly removes the option or forces “Keep files only.” That’s not Windows being evil. That’s Windows refusing to promise a migration it can’t complete.
Disk health and file system inconsistencies
An in-place upgrade is a huge file operation: copy, unpack, stage, move, hardlink, and rollback. Disks that “mostly work” turn into disks that fail consistently under this load. If you see disk timeouts or NTFS event IDs, treat it like a hardware incident, not an OS incident.
Not enough space for staging and rollback
Setup needs room for:
- install image expansion,
- driver and migration caches,
- rollback state,
- log files that can get large during repeated attempts.
If you’re low on space, Setup can fail late, roll back, and leave you exactly where you started—just more tired.
Security and endpoint tooling hooks
Endpoint protection, DLP, VPN clients, and disk encryption tools often install kernel drivers, network filters, and system services. During a repair install, Windows may disable or remove incompatible components. You “kept apps,” but the apps that make the device usable in a corporate network might be broken.
Licensing tied to machine identity
Some software binds licenses to hardware IDs, Windows install IDs, TPM state, or registry keys that may change during a repair install. Most of the time, it’s fine. When it isn’t, it’s urgent and expensive.
Joke #2: Licensing servers can smell fear. They also seem to know when it’s Friday.
Common mistakes (symptom → root cause → fix)
1) “Keep apps” option is missing in Windows Setup
Symptom: Setup only offers “Keep personal files only” or “Nothing.”
Root cause: Media mismatch (edition/language/build), booted from USB instead of running in-OS, or unsupported upgrade path.
Fix: Boot into Windows, mount the correct ISO, run setup.exe. Confirm edition with DISM before starting.
2) In-place upgrade fails and rolls back after a long wait
Symptom: Hours of progress, then “Undoing changes.”
Root cause: Insufficient disk space, driver incompatibility, or file system errors.
Fix: Free space, remove/disable third-party AV/VPN temporarily, run chkdsk, read Panther logs. Don’t re-run blindly.
3) After “Reset this PC (keep my files),” apps are gone
Symptom: Desktop apps missing; user shocked.
Root cause: Reset is designed to remove installed applications.
Fix: Only use Reset when you have a reinstall plan (MDM, SCCM, Intune, or manual installers) and license recovery plan.
4) Device boots but corporate network access is broken
Symptom: Wi-Fi works, but VPN/802.1X/cert-based auth fails.
Root cause: Network filter drivers, certificates, or management agents were removed/invalidated.
Fix: Re-enroll device, reinstall VPN client, restore certificates, confirm time sync, validate NLA and services.
5) BitLocker recovery key prompt appears unexpectedly
Symptom: After reboot, BitLocker asks for recovery key.
Root cause: TPM measurements changed (firmware changes, boot config changes), or BitLocker wasn’t suspended during major OS changes.
Fix: Retrieve key from your directory/account vault, suspend protection before repair operations when appropriate, and ensure secure boot settings are stable.
6) System is “fixed” but updates still fail
Symptom: Repair install completed, yet Windows Update errors persist.
Root cause: Underlying servicing stack issues, policy restrictions, or network/proxy/WSUS problems rather than OS corruption.
Fix: Validate update source configuration, check event logs, confirm connectivity, inspect Windows Update policies and services.
7) Apps are “kept” but behave like first run / lost settings
Symptom: Apps open, but profiles/configs missing.
Root cause: User profile corruption, profile rebuild, redirected folders, or app data stored in locations not migrated cleanly.
Fix: Verify user profile integrity, restore app-specific data directories, avoid deleting AppData blindly during cleanup.
Checklists / step-by-step plan
Decision checklist: pick the right recovery path
- If you can’t boot into Windows: you are unlikely to do a true “keep apps” repair install. Consider image restore, offline repair, or clean install with data recovery.
- If disk health is questionable: stop and image/backup first. OS operations don’t fix hardware.
- If you need apps preserved: plan an in-place upgrade repair install, not Reset.
- If you need security certainty: clean install is the right answer. Persistence can preserve badness too.
Pre-flight checklist (do this before you touch Setup)
- Confirm edition and build (Tasks 1–2).
- Confirm free space (Task 3).
- Confirm BitLocker recovery key availability (Task 4).
- Run
chkdskscan and repair as needed (Task 6). - Run SFC and DISM (Tasks 7–8).
- Export installed app inventory (Task 11).
- Identify critical drivers and VPN/AV components (Task 12).
- Confirm activation channel (Task 13).
Step-by-step: in-place upgrade repair install that actually keeps apps
- Get correct install media: same OS major version, same edition, same language, same architecture (x64 vs ARM64). Prefer equal or newer build.
- Boot into Windows normally: don’t start by booting from USB.
- Temporarily disable or uninstall third-party AV/VPN/DLP if your environment permits. These drivers frequently cause Setup failures.
- Mount ISO and run
setup.exe. - Choose: “Keep personal files and apps.” If it’s not offered, stop and reassess—don’t “hope.”
- After completion: verify network stack, device management enrollment, and security tooling health before declaring victory.
- Then patch: run Windows Update and confirm the original issue is gone.
Step-by-step: when you must clean install (and still minimize pain)
- Backup user data (documents, desktop, downloads) and app-specific data locations.
- Export app inventory and licensing info where possible.
- Confirm recovery keys and activation paths.
- Clean install Windows using correct edition.
- Install drivers (chipset/network/storage) first, then management agent, then security tooling, then business apps.
- Restore data, then validate app configs and sign-ins.
FAQ
1) Can I reinstall Windows 11 and keep all my installed programs?
Only via an in-place upgrade repair install run from inside Windows, with compatible media and a supported migration path. Reset won’t keep desktop programs.
2) Does “Reset this PC” keep apps?
No for traditional desktop apps. “Keep my files” means user data stays, apps go. Plan accordingly.
3) If I install Windows over the top without formatting, will my apps still work?
Usually no. You may get Windows.old with your old files, but installed programs won’t be registered and won’t run as installed.
4) Why does Windows Setup sometimes hide the “keep apps” option?
Because it detected a mismatch (edition/language/build/architecture) or you started Setup from boot media. Setup won’t promise what it can’t migrate.
5) Do Microsoft Store apps survive a reinstall?
Sometimes. Store apps are package-based and can be re-registered, but a clean install still requires reinstallation. Don’t count on them surviving a wipe.
6) Will an in-place upgrade fix broken Windows Update?
Often, yes—especially when the component store or system files are corrupted. But if your update source/policies are wrong (WSUS/proxy), you’ll still fail after the repair.
7) What about drivers—will they be preserved?
Many drivers carry over, but problematic kernel drivers (VPN, AV, storage filters) can be removed or replaced. Always verify network and storage functionality afterward.
8) How do I reduce the risk of losing software licenses?
Inventory software, capture license keys where applicable, confirm vendor reactivation policies, and avoid unnecessary hardware/TPM changes during the process.
9) If the machine won’t boot, is “keep apps” still possible?
Not in the normal supported sense. If you can’t run Setup from within Windows, the migration logic that keeps apps usually can’t run. Consider restore from image or clean install with data recovery.
10) Should I do SFC/DISM before reinstalling?
Yes. They’re low-risk and frequently fix the issue without any reinstall. If they fail, you’ve also gathered evidence that supports moving to an in-place upgrade.
Conclusion: next steps that won’t hurt
If you remember one thing: “Keep apps” is not a vibe; it’s a specific procedure. The in-place upgrade repair install is the closest thing to “reinstall Windows and keep apps,” and it only works when you run it from within a booted Windows environment with compatible media and a reasonably healthy disk.
Next steps:
- Run the fast diagnosis checks: bootability, disk health signals, BitLocker status, free space.
- Try SFC and DISM before you reinstall anything.
- If you truly need apps preserved, plan an in-place upgrade repair install and validate media compatibility first.
- If the device is untrusted, unstable, or the disk is failing, stop chasing “keep apps” and do a clean install or image restore with a controlled app redeploy.