Update failed: Cumulative Update for Windows 11, version 25H2 for x64-based Systems (KB5070773) (26200.6901)

Good — thanks for the screenshot. R: clearly contains a small recovery area (Recovery folder, System Volume Information, a small .CBM file). That tells us it’s a recovery partition, not user data. You have two safe choices:
  • Hide it (recommended, safe, reversible) — simply remove the drive letter so it won’t show in Explorer. No data removed.
  • Delete it (only if you have a disk image / recovery USB and are OK losing the OEM recovery) — frees the 700+ MB and lets you potentially expand C:.
I’ll give the exact checks and commands (copy/paste) so you can do either. Do these steps in an elevated PowerShell (Run as Administrator). Stop after any step if you want me to confirm the output.
1) Confirm Windows Recovery Environment (WinRE) location (important)
This tells us where the active WinRE is hosted — if it points to R: we should not delete R: unless we reconfigure WinRE first.
Run:
reagentc /info
  • If "Windows RE location" shows a path on R: (for example R:\Recovery\WindowsRE\Winre.wim) then R: contains the active WinRE and you should not delete it until you move or disable WinRE.
  • If it points to a different partition (or WinRE is Disabled), deletion is less risky (still backup first).
Paste the reagentc output here if you want me to interpret it.
2) (Recommended) Hide R: by removing its drive letter
This is reversible and keeps the recovery partition intact.
a) Find the partition that corresponds to R:
Get-Partition -DriveLetter R | Format-List *
b) Remove the access path (hide):

Replace the partition number/ disk number if the above shows different values​

$part = Get-Partition -DriveLetter R
Remove-PartitionAccessPath -DiskNumber $part.DiskNumber -PartitionNumber $part.PartitionNumber -AccessPath "R:\"
After that, R: will disappear from File Explorer but the partition remains.
3) If you want to delete R: (only after full image + recovery USB)
Prerequisites (must do before deleting)
  • Create a full disk image (Macrium Reflect or similar) OR ensure you have a full reinstall/recovery plan.
  • Create a Windows recovery USB (Settings → Recovery → Create a recovery drive) or use Media Creation Tool to create install media.
  • Confirm reagentc /info does NOT list WinRE on R: (if it does, use reagentc to relocate or disable WinRE first).
If prereqs are done, delete the partition:
a) Confirm partition number:
Get-Partition -DriveLetter R | Format-List DiskNumber,PartitionNumber,Size
b) Delete partition (this permanently removes it):

Replace DiskNumber and PartitionNumber from the previous command​

diskpart
select disk 0
select partition 4
delete partition override
exit
(Or in PowerShell)
$part = Get-Partition -DriveLetter R
Remove-Partition -DiskNumber $part.DiskNumber -PartitionNumber $part.PartitionNumber -Confirm:$false
c) Reclaim/extend C: (if unallocated space sits directly after C
  • If Disk Management shows unallocated space immediately to the right of C:, you can right‑click C: → Extend Volume.
  • In PowerShell (replace NewSize with desired final size in bytes — easier via Disk Management):
    Resize-Partition -DriveLetter C -Size ((Get-PartitionSupportedSize -DriveLetter C).SizeMax)
If the unallocated block is not adjacent to C: (there are other partitions between)
  • Windows Disk Management cannot extend C: across those; you’ll need a third‑party partitioning tool (MiniTool / AOMEI / GParted) to move partitions. Do that only from a full disk image backup.
4) If WinRE is currently on R: and you want to delete R: safely
Move WinRE to the EFI/System partition first (example — check your EFI drive letter; suppose it is S: — confirm first):
  • Mount EFI/System partition if not lettered (assign a temp letter S):
    $efi = Get-Partition -Type System
    Add-PartitionAccessPath -DiskNumber $efi.DiskNumber -PartitionNumber $efi.PartitionNumber -AccessPath "S:\"
  • Copy WinRE and update reagentc:
    mkdir S:\Recovery\WindowsRE
    robocopy R:\Recovery\WindowsRE S:\Recovery\WindowsRE /E
    reagentc /setreimage /path S:\Recovery\WindowsRE
    reagentc /enable

    Verify​

    reagentc /info
Only after WinRE shows location on S: and reagentc /info shows Enabled is it safe to delete R:.
5) Quick safety checklist before doing anything destructive
  • Backup: full disk image or at least your user data externally.
  • Recovery media: create a Windows USB recovery/install drive.
  • Verify reagentc /info and that you can boot from recovery media.
  • If in doubt, choose “hide” (remove drive letter) — reversible and safe.
Which do you want to do now?
  • “Hide R:” — I’ll give the one‑line to remove the drive letter and we’ll stop.
  • “Delete R: (I made backups)” — I’ll give the exact diskpart commands (I’ll wait while you confirm reagentc output and that you have a recovery USB).
  • “Move WinRE from R: to EFI then delete” — I’ll walk through the safe copy + reagentc steps.
Tell me which and I’ll provide the exact copy/paste commands and wait while you run them.
 
Thanks — your reagentc output confirms Windows RE is currently located on partition 3 (the partition you see as R. That means R: is the active recovery partition and should not be deleted unless you first move the WinRE image somewhere else (or you have a full image + recovery USB and accept losing that recovery data).
Two safe, practical choices (recommended order)
  • Option 1 — Hide R: (recommended, reversible, no risk)
    • Remove the assigned drive letter so R: (and System Reserved) no longer appear in File Explorer. The partition and WinRE remain intact and nothing is deleted.
  • Option 2 — Remove R: permanently (only if you have a full disk image / recovery USB and you want to reclaim the space)
    • Move WinRE to the EFI/System partition first (so recovery still works), verify reagentc reports the new location, then delete the R: partition and optionally extend C:. This is more work but possible. Do NOT delete R: until you confirm WinRE was moved and you have backups.
Which I suggest now
  • If you just want it gone from view: hide the partition (Option 1). That’s simple and reversible.
  • If you want the space merged into C: later, do Option 2 — but only after making a full image and a recovery USB.
Exact commands — copy/paste into an elevated PowerShell (I’ll give Option 1 first; then Option 2 if you want it)
OPTION 1 — Hide the partitions (remove drive letters)
1) Confirm the partition(s) to remove letters from:
Get-Partition -DiskNumber 0 | Format-Table PartitionNumber,DriveLetter,Size,Type -AutoSize
2) Remove the drive letter for R: and for System Reserved (E so they stop showing:

Remove R:​

$partR = Get-Partition -DriveLetter R
Remove-PartitionAccessPath -DiskNumber $partR.DiskNumber -PartitionNumber $partR.PartitionNumber -AccessPath "R:\"

Remove System Reserved (example DriveLetter E)​

$partE = Get-Partition -DriveLetter E
Remove-PartitionAccessPath -DiskNumber $partE.DiskNumber -PartitionNumber $partE.PartitionNumber -AccessPath "E:\"
3) Verify they are hidden:
Get-Partition -DiskNumber 0 | Format-Table PartitionNumber,DriveLetter,Size,Type -AutoSize
If you later want them visible again, reassign a letter:
Add-PartitionAccessPath -DiskNumber <disk#> -PartitionNumber <part#> -AccessPath "R:\"
OPTION 2 — Permanently remove R: (only after backup + moving WinRE)
Important pre-steps (MUST DO before deletion)
  • Make a full disk image (Macrium, etc. and create a Windows recovery USB.
  • Confirm reagentc currently points to R: (you already did). We will move WinRE to the EFI/System partition.
A. Find the EFI/System partition and assign a temporary letter (S

Find the System partition (Type = System)​

$efi = Get-Partition -DiskNumber 0 | Where-Object { $.Type -eq 'System' -or $.GptType -like 'EFI' }

Assign letter S (only for this session)​

Add-PartitionAccessPath -DiskNumber $efi.DiskNumber -PartitionNumber $efi.PartitionNumber -AccessPath "S:\"
B. Copy WinRE from R: to the EFI partition and set it as the WinRE location

Create folder and copy​

New-Item -Path "S:\Recovery\WindowsRE" -ItemType Directory -Force
robocopy "R:\Recovery\WindowsRE" "S:\Recovery\WindowsRE" /E

Update reagentc to point at the new location and enable​

reagentc /setreimage /path S:\Recovery\WindowsRE
reagentc /enable

Verify​

reagentc /info
C. If reagentc /info now shows Windows RE location on the EFI/System partition and Status = Enabled, delete R:

Identify R partition number first:​

$partR = Get-Partition -DriveLetter R

Delete (PowerShell)​

Remove-Partition -DiskNumber $partR.DiskNumber -PartitionNumber $partR.PartitionNumber -Confirm:$false
Alternatively using diskpart if you prefer:
diskpart
select disk 0
select partition <#> (use the partition number from Get-Partition)
delete partition override
exit
D. Reclaim/extend C: (only if unallocated space is adjacent)
  • If unallocated space appears directly after C:, extend:
    Resize-Partition -DriveLetter C -Size ((Get-PartitionSupportedSize -DriveLetter C).SizeMax)
  • If unallocated space is not adjacent you will need a partition tool (GParted / MiniTool / AOMEI) to move partitions; only do that from a verified disk image backup.
E. Remove the temporary access path to S:
Remove-PartitionAccessPath -DiskNumber $efi.DiskNumber -PartitionNumber $efi.PartitionNumber -AccessPath "S:\"
Final safety checks
  • After any deletion, reboot and confirm Windows boots normally.
  • Run reagentc /info and bcdedit /enum ALL to confirm WinRE and Boot Manager are intact.
  • If anything fails, boot from your recovery USB and run Startup Repair or use bcdboot (example):
    bcdboot C:\Windows /s S: /f UEFI (only if S: is your EFI partition)
Summary recommendation for your case
  • Because R: currently hosts WinRE (reagentc showed partition3), DO NOT delete R: unless you first move WinRE to the EFI partition and have a full image + recovery USB.
  • If you just want it hidden, remove the drive letter for R: (Option 1) — that’s quick and safe and I can give the one‑line for you to run now.
If you want to proceed now
  • Tell me “Hide R now” and I’ll give the exact single Remove-PartitionAccessPath command for your system (or run the small sequence above while you watch).
  • Or tell me “Move WinRE and delete R” and I’ll walk you through Option 2 step‑by‑step and wait at each step.
Which do you want to do?
 
Okay — here are the exact, safe commands to hide (remove the drive letters for) both R: (your recovery partition) and the System Reserved partition (E and how to undo it if needed. Run everything in an elevated PowerShell (right‑click PowerShell → Run as administrator). Don’t delete anything — these commands only remove the drive letters so the partitions no longer show in File Explorer.
Step 1 — one‑line commands to hide R: and E:
Run these two lines (Admin PowerShell):

remove R: (Recovery)​

$partR = Get-Partition -DriveLetter R
if ($partR) { Remove-PartitionAccessPath -DiskNumber $partR.DiskNumber -PartitionNumber $partR.PartitionNumber -AccessPath "R:\" }

remove E: (System Reserved)​

$partE = Get-Partition -DriveLetter E
if ($partE) { Remove-PartitionAccessPath -DiskNumber $partE.DiskNumber -PartitionNumber $partE.PartitionNumber -AccessPath "E:\" }
What these do
  • They find the partition currently mounted as R: or E: and remove the mount point (drive letter). The partitions and their contents remain intact — you’re only hiding them from Explorer.
Step 2 — verify the letters are gone
Run (Admin PowerShell):
Get-Partition -DiskNumber 0 | Format-Table PartitionNumber,DriveLetter,Size,Type -AutoSize
You should see those partitions listed but with DriveLetter blank (no letter). Also File Explorer should no longer show System Reserved or Local Disk (R.
Step 3 — confirm WinRE still valid (optional quick check)
Run (Admin PowerShell):
reagentc /info
  • Windows RE status should remain Enabled and Windows RE location should still point to the recovery partition (device path). Removing the drive letter does not break WinRE.
How to put the letters back (undo)
If you need the partitions visible again, run these (Admin PowerShell) — choose unused letters if R/E already used:
Add-PartitionAccessPath -DiskNumber $partR.DiskNumber -PartitionNumber $partR.PartitionNumber -AccessPath "R:\"
Add-PartitionAccessPath -DiskNumber $partE.DiskNumber -PartitionNumber $partE.PartitionNumber -AccessPath "E:\"
(Or use Disk Management GUI to assign a letter.
Notes & safety
  • This is reversible and safe — it does not delete any data.
  • If you later want to reclaim the space and extend C: you’ll need to move/delete partitions; do that only after making a full disk image backup.
  • If you prefer I can run the exact commands while you watch and then confirm the output — say “Run them now” and I’ll wait for you to paste the results or to confirm success.
Would you like me to wait while you run those two Remove-PartitionAccessPath lines and paste the Get-Partition output?
 
No problem — “hide” is exactly what the commands I gave do (they remove the drive letters so the partitions aren’t visible). Below are the precise, safe copy/paste commands again (they only hide the partitions — nothing is deleted). Run them in an elevated PowerShell (right‑click PowerShell → Run as administrator).
1) Hide (remove the drive letters for) R: and E:

Remove R: (Recovery)​

$partR = Get-Partition -DriveLetter R
if ($partR) { Remove-PartitionAccessPath -DiskNumber $partR.DiskNumber -PartitionNumber $partR.PartitionNumber -AccessPath "R:\" }

Remove E: (System Reserved)​

$partE = Get-Partition -DriveLetter E
if ($partE) { Remove-PartitionAccessPath -DiskNumber $partE.DiskNumber -PartitionNumber $partE.PartitionNumber -AccessPath "E:\" }
2) Verify they are hidden
Get-Partition -DiskNumber 0 | Format-Table PartitionNumber,DriveLetter,Size,Type -AutoSize
You should see those partitions listed but with DriveLetter blank.
3) Quick check that WinRE still works (optional)
reagentc /info
Windows RE should still show Enabled and its location — removing the letters does not disable WinRE.
4) How to undo (put the letters back)
If you later want them visible again, run (replace X/Y with the right DiskNumber/PartitionNumber if needed or use these to reassign the same letters):
Add-PartitionAccessPath -DiskNumber $partR.DiskNumber -PartitionNumber $partR.PartitionNumber -AccessPath "R:\"
Add-PartitionAccessPath -DiskNumber $partE.DiskNumber -PartitionNumber $partE.PartitionNumber -AccessPath "E:\"
Or you can use Disk Management (diskmgmt.msc) to reassign/restore letters.
Notes / Safety
  • These commands are reversible and do not delete any data.
  • Run them only in an elevated PowerShell.
  • If anything looks unexpected after you run them, paste the output of the verification command above and I’ll confirm.
Would you like me to wait while you run those two remove commands and then check the Get-Partition output? I can verify the results for you.
 
Good — thanks for confirming R: and the System Reserved letter are hidden and WinRE is intact. Nice and safe.
Next: restoring files & apps. I’ll keep this focused and give you exact, tested commands you can run (or run with me watching). Do these in the order shown, and stop if anything looks unexpected.
Important safety reminders before we change anything
  • You already converted the disk and ran a repair — create a quick image or at least a System Restore point if you haven’t yet. (Optional but recommended.
  • Don’t try to reinstall large apps while Kaspersky or other protections are paused; re‑enable them afterward.
A — Confirm Windows.old exists (safe check)
Run (Admin PowerShell):
Test-Path C:\Windows.old
If it returns True, the old installation is present and you can copy files from it. If False, the old install was removed and you’ll need to reinstall apps from vendor installers.
B — Recover personal files (Desktop, Documents, Pictures) — safe, reversible
These robocopy commands copy everything and preserve timestamps/ACLs. Replace %USERNAME% if you prefer the literal name — these work in PowerShell/CMD.
Run as Administrator:

Desktop​

robocopy "C:\Windows.old\Users\%USERNAME%\Desktop" "$env:USERPROFILE\Desktop" /E /COPYALL /R:1 /W:1

Documents​

robocopy "C:\Windows.old\Users\%USERNAME%\Documents" "$env:USERPROFILE\Documents" /E /COPYALL /R:1 /W:1

Pictures​

robocopy "C:\Windows.old\Users\%USERNAME%\Pictures" "$env:USERPROFILE\Pictures" /E /COPYALL /R:1 /W:1

Downloads (if you want)​

robocopy "C:\Windows.old\Users\%USERNAME%\Downloads" "$env:USERPROFILE\Downloads" /E /COPYALL /R:1 /W:1
Notes:
  • Robocopy will skip duplicates and retry minimal times (/R:1 /W:1).
  • Check results and then remove C:\Windows.old only when you’re satisfied.
C — Restore browser profiles (Chrome example)
If Chrome was removed but you want to restore the user profile (bookmarks, history, extensions data):
1) Close Chrome completely.
2) Copy the profile folder:
robocopy "C:\Windows.old\Users\%USERNAME%\AppData\Local\Google\Chrome\User Data" "$env:LOCALAPPDATA\Google\Chrome\User Data" /E /COPYALL /R:1 /W:1
3) Start Chrome — your profile should reappear (sign back into Google to restore sync).
Edge profile path is similar (AppData\Local\Microsoft\Edge\User Data).
D — Restore Start menu shortcuts & Taskbar pins
1) Copy Start Menu shortcuts (Programs) from Windows.old:
robocopy "C:\Windows.old\Users\%USERNAME%\AppData\Roaming\Microsoft\Windows\Start Menu\Programs" "$env:APPDATA\Microsoft\Windows\Start Menu\Programs" /E /COPYALL
2) Taskbar pins aren’t trivially restored; you’ll need to re-pin apps manually. You can re‑pin shortcuts from the Start Menu location after the copy completes.
E — Reinstall large applications (Office, Adobe)
  • Microsoft Office:
    • If Office 365 / Microsoft 365: go to account.microsoft.com → Services & subscriptions → install. Sign in with the Microsoft account used previously.
    • If you have a boxed/retail key: use the installer from Microsoft and enter your product key.
  • Adobe Creative Cloud:
    • Download and install the Creative Cloud app from adobe.com, sign in, and reinstall apps from your Adobe account.
  • For each large app, prefer the vendor’s official download and sign-in flow — it will restore licenses and settings where possible.
F — Repair apps if executable files remain
  • If program folders exist under C:\Program Files\ or C:\Program Files (x86), check the vendor’s installer for a Repair option (Programs & Features → select app → Repair) before reinstalling.
G — Recreate missing associations / defaults
  • If file types are still opening with Edge or other unexpected apps, set defaults:
    • Settings → Apps → Default apps → choose app → assign protocols (.htm, .html, HTTP, HTTPS) to your preferred browser.
    • Or run Start-Process ms-settings:defaultapps.
H — Create a restore point / image (recommended)
After you’ve restored your files and reinstalled apps, create a System Restore point and/or a full disk image so you won’t have to repeat this.
I — If you want me to do it step‑by‑step with you
Tell me which of these you want to do first:
1) Recover Desktop/Documents (robocopy) — I’ll wait while you run the commands and verify results.
2) Restore Chrome profile (robocopy) — I’ll wait and check.
3) Reinstall Office/Adobe — I’ll guide account/installer steps.
4) Collect logs (if anything went wrong with the in‑place repair) — I’ll parse and advise.
If you pick (1) or (2) I’ll paste the exact robocopy commands again for you to copy/paste and then wait while you run them and tell me the output. If you want to do everything tomorrow, we can schedule it stepwise so it’s not overwhelming.
Which would you like to do first?
 
Second issue is that Windows keeps asking my PIN whenever I do something like when autofill password. I want to disable this.
 
Good — that prompt is coming from the browser/OS asking you to confirm you with Windows Hello (PIN/fingerprint) before automatically filling sensitive credentials. You can stop those prompts, but it reduces the protection that prevents someone with physical access from using saved passwords. I’ll give concise, safe options (recommended first), exact menu steps for the common browsers, and what to do if you want to remove the PIN completely.
Quick summary — the safe choices
  • Recommended (best balance): Turn off “Require Windows Hello for password autofill” in your browser(s). This stops the PIN prompt for autofill but keeps your PIN for sign-in.
  • Less secure: Remove your Windows Hello PIN entirely (so the OS won’t prompt because there’s no PIN) — not recommended.
  • If a particular app (not the browser) is prompting, you’ll need to adjust that app’s settings or sign-in method.
Exact steps — do these first (Edge and Chrome cover most cases)
1) Microsoft Edge — turn off Windows Hello for Autofill
  • Open Edge.
  • Go to Settings → Profiles → Passwords.
  • Look for the setting labeled something like:
    • “Require Windows Hello to fill in passwords” or
    • “Use Windows Hello to sign in to websites” (wording varies by version).
  • Turn that option OFF.
  • Optional: also turn OFF “Auto sign‑in” if you don’t want sites to sign you in automatically.
That will stop Edge asking for your PIN every time it fills a password.
2) Google Chrome (if you use it)
Chrome can also ask for confirmation if you use Windows platform authentication or if Chrome is set to auto sign-in.
  • Open Chrome → Settings → Autofill → Passwords.
  • Turn OFF:
    • “Auto Sign‑in” (automatically signs you into websites).
    • “Offer to save passwords” if you want Chrome not to store them at all.
      Chrome does not always use Windows Hello by default; if you see a prompt there, disabling Auto Sign‑in will prevent immediate sign-in attempts that trigger the PIN prompt.
3) Firefox (if you use it)
  • Open Firefox → Settings → Privacy & Security → Logins and Passwords.
  • Turn OFF “Autofill logins and passwords” or uncheck “Ask to save logins and passwords for websites”.
4) System-level: stop Windows asking for PIN for credential operations (NOT recommended unless you accept the risk)
Two possibilities:
A) Remove Windows Hello PIN entirely
  • Settings → Accounts → Sign‑in options → PIN (Windows Hello) → Remove.
    • You’ll be prompted for your current Windows password to confirm.
    • After removal, Windows will not prompt for a PIN, but you’ll lose the convenience and the security benefit of Windows Hello.
B) Disable Windows Hello requirement for Microsoft accounts
  • Settings → Accounts → Sign‑in options → look for “Require Windows Hello sign-in for Microsoft accounts” and turn it OFF.
    • This affects Microsoft-account features and some sync/auth prompts, but may not stop every prompt.
5) If some third‑party app still asks for PIN when filling passwords
  • That app is intentionally using Windows Hello to secure access to sensitive credentials. Check the app’s settings for an option to disable “Use Windows Hello” or similar.
  • If not present and you want no prompts anywhere, removing the PIN (step 4A) is the only guaranteed system‑wide way — again, not recommended for security reasons.
6) Reboot not required in most cases
  • Changing the browser setting (Edge/Chrome) takes effect immediately — no reboot required.
  • Removing the PIN will not require a reboot, but sign‑in behavior changes immediately.
Security tradeoffs — briefly
  • Turning off the browser’s “Require Windows Hello” means anyone who gets access to your unlocked Windows account can have browser autofill fill passwords without an extra PIN check. That’s less secure but more convenient.
  • Removing the PIN reduces security further — if someone has your Windows password or your account is left unlocked, they can sign in or perform sensitive actions more easily.
What I suggest you do now
  • If Edge is the one asking PINs most often: follow step 1 and disable the “Require Windows Hello to fill passwords” option in Edge first. That’s the least intrusive and should stop the behavior you described.
  • If after that some other browser or app still prompts, let me know which app and I’ll give the exact toggle for it.
If you want, say “Disable Edge PIN prompt” and I’ll give that exact setting location again and wait while you turn it off. Or tell me which browser(s) you use and I’ll list the exact steps for each.
 
Okay — sounds good. Before we jump back to file recovery I can run through a quick checklist and surface any important post‑repair problems so we don’t miss anything. Tell me which you want to do now, or I can run the short diagnostic set and post the results for you to review.
Suggested priority (order I recommend)
1) Confirm system stability & activation (Windows is activated, no driver or critical errors).
2) Confirm Windows Update / KB status (you already confirmed KB5070773 — we’ll recheck other updates).
3) Check disk/SMART health and available free space.
4) Inspect Device Manager for missing drivers.
5) Find any recent critical errors in System/Application event logs.
6) If all OK, proceed with restoring files (robocopy) and then reinstalling apps.
If you want me to run diagnostics now (I’ll wait while you run them), copy‑paste these three admin PowerShell commands and paste the outputs here (they’re short and give a lot of useful info):
1) Windows activation + basic system info
slmgr /xpr
systeminfo | Select-String 'OS Name|OS Version|System Type|Total Physical Memory'
2) Disk health and partition layout
Get-PhysicalDisk | Format-Table FriendlyName,SerialNumber,MediaType,HealthStatus,OperationalStatus -AutoSize
Get-Partition -DiskNumber 0 | Format-Table PartitionNumber,DriveLetter,Size,Type -AutoSize
3) Recent critical System events (last 6 hours)
Get-WinEvent -FilterHashtable @{LogName='System'; Level=2; StartTime=(Get-Date).AddHours(-6)} | Select TimeCreated, ProviderName, Id, Message -First 30
Or, if you prefer GUI checks, tell me and I’ll give step‑by‑step for Device Manager, Event Viewer, and Windows Update history.
Which do you want to do now?
  • “Run diagnostics” — I’ll wait for the outputs from the three commands above and interpret them.
  • “I’ll list issues” — tell me the specific problems you’re seeing and I’ll address those first.
  • “Skip diagnostics — restore files” — I’ll repost the robocopy commands and we’ll start recovering Desktop/Documents.
Your call.
 
Actually, my third issue was removing PIN request at sign-in at boot. I want Windows to boot without any user intervention ie no PIN or password.
 
Okay — we can remove the PIN and set Windows to log in automatically, but two important warnings first:
  • Security: automatic sign‑in (no PIN or password at boot) means anyone with physical access to the PC can get into your account. Don’t do this on a laptop or any machine that could be lost/stolen or used by others.
  • Backup: if something goes wrong, you should have a recovery USB or system image. You already created recovery media earlier — good.
Tell me before we proceed: is the account you sign in with a Microsoft account (email) or a local account? The steps differ slightly (Microsoft accounts require your Microsoft password for auto‑login, or you can switch to a local account).
I’ll give two short workflows (GUI + preferred secure tool). Pick which you want and I’ll wait while you run it:
A — Recommended (clean + safer): Remove PIN via Settings, then enable Autologon with Sysinternals Autologon
Why: removes Windows Hello PIN and uses Microsoft’s Autologon tool to store credentials securely (it encrypts them). Safer than storing plain text in the registry.
Steps (run as you prefer — I’ll wait if you want me to):
1) Remove the Windows Hello PIN
  • Settings → Accounts → Sign‑in options → Windows Hello PIN → Remove.
    You’ll be asked to confirm with your account password. Complete that.
If Remove is greyed out or fails, tell me and I’ll give the safe command to clear the PIN store.
2) Download Autologon (one‑time)
  • Download Autologon from Microsoft Sysinternals (search “Autologon Sysinternals” or go to Microsoft Sysinternals site).
  • Save and unzip; you’ll run Autologon.exe as admin.
3) Run Autologon
  • Right‑click Autologon.exe → Run as administrator.
  • In the dialog enter:
    • Username (your account name; for Microsoft account use the full email)
    • Domain (leave blank or use the computer name for local accounts)
    • Password (your Microsoft account password if that’s the account)
  • Click Enable. You’ll get a confirmation that Autologon is enabled and credentials are stored encrypted.
4) Test
  • Reboot. Windows should sign in automatically to the account you configured.
To disable Autologon later, run Autologon.exe and click Disable.
B — Quick GUI method (netplwiz) — simpler but stores credentials less securely for Microsoft accounts
1) Remove PIN first (same as Step A1 above).
2) Enable auto‑login via User Accounts UI
  • Press Win+R, type netplwiz and press Enter.
  • In the Users window uncheck “Users must enter a user name and password.”
  • Click Apply. A dialog asks for the user name and password to use for automatic sign‑in: enter them (Microsoft password if that is the account). Click OK.
3) Reboot to test.
Notes about Microsoft accounts and netplwiz:
  • netplwiz will accept your Microsoft account password. But the password will be stored in the registry (less ideal). Autologon stores it encrypted and is preferred.
C — If Settings won’t remove the PIN (power user option)
If the Remove button is missing or fails, you can clear the PIN data by deleting the NGC folder (this forces Windows to remove all PIN/Windows Hello data for all accounts on the machine). This is a more intrusive step; only use if Remove doesn’t work.
If you want to try it (I’ll wait and walk you through), these are the exact admin commands (one block). They take ownership of the NGC folder and delete it — you will need to set up new Windows Hello sign‑ins later if you want them.
Run as Administrator (PowerShell / CMD):
takeown /F "C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\NGC" /R /D Y
icacls "C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\NGC" /grant Administrators:F /T /C
rd /s /q "C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\NGC"
After that, reboot. Then set the automatic sign‑in (Autologon or netplwiz) as above.
Which workflow do you want to use now?
  • “A — Autologon (recommended)” — I’ll wait while you remove the PIN and I’ll provide the Autologon steps and check.
  • “B — netplwiz (quick)” — I’ll wait while you remove the PIN and use netplwiz.
  • “C — Force remove PIN (NGC) then Autologon” — I’ll give the takeown/icacls/rd commands and wait for your confirmation before running them.
Tell me which option and whether your account is a Microsoft account or local account, and I’ll guide the next step precisely and wait for your result.
 
Thanks — I can see you’re signed in with your Microsoft account (your email is shown in Settings). That’s fine; here are two safe, short ways to remove the PIN and enable automatic sign‑in. I recommend the Sysinternals Autologon method (it stores credentials encrypted) when using a Microsoft account.
Important security reminder (read first)
  • Automatic sign‑in means anyone with physical access to the PC can get into your account. Don’t enable this on a laptop or on any machine that others can access. If you’re happy with the risk, proceed.
A — Recommended: Remove PIN, then enable Autologon (Sysinternals)
1) Remove the PIN (GUI)
  • Settings → Accounts → Sign‑in options → Windows Hello PIN → Remove.
  • You will be asked to confirm with your Microsoft account password.
2) Download Autologon (Sysinternals)
3) Run Autologon as Administrator
  • Right‑click Autologon.exe → Run as administrator.
  • In the dialog:
    • Username: use your full Microsoft email (e.g. rupesh@patre.com).
    • Domain: leave blank (or use the PC name for local accounts).
    • Password: enter your Microsoft account password.
  • Click Enable. You’ll get confirmation that autologon is enabled.
4) Test — reboot the PC
  • Reboot and confirm Windows signs in automatically. To disable later, run Autologon.exe and click Disable.
B — Quick alternative (netplwiz) — simpler but less secure for Microsoft accounts
1) Remove PIN as above.
2) Press Win+R, type netplwiz, Enter.
3) Uncheck “Users must enter a user name and password”. Click Apply.
4) When prompted, enter the account username (use full Microsoft email) and password. Click OK.
5) Reboot and confirm auto sign‑in works.
  • Note: this stores credentials in the registry and is less secure than Autologon.
C — If Settings will not let you remove the PIN (power‑user fallback)
If the Remove button is unavailable or the removal fails you can delete the NGC folder (this clears Windows Hello / PIN for all accounts). This is more intrusive; do it only if Remove fails.
Run these as Administrator (PowerShell / CMD):
takeown /F "C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\NGC" /R /D Y
icacls "C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\NGC" /grant Administrators:F /T /C
rd /s /q "C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\NGC"
  • Reboot after this. Then remove a PIN or set up autologon as in A or B.
D — Verify & revert
  • Verify PIN removed: Settings → Accounts → Sign‑in options (PIN section should show option to Set up, not Remove).
  • To revert autologon: run Autologon.exe → Disable, or re‑check “Users must enter a user name and password” in netplwiz.
E — If you want, I’ll:
  • Wait while you remove the PIN and enable Autologon (say “I’ll run Autologon now”) and help if anything fails, or
  • Give the exact commands again for the NGC deletion if Remove is greyed out.
Which path do you want to follow now — A (Autologon, recommended) or B (netplwiz quick)? I’ll wait and guide any step you run.
 
Thanks — since you use a Microsoft account, here’s a short, safe plan to remove the PIN and enable automatic sign‑in. I recommend the Sysinternals Autologon tool (stores credentials encrypted) — safer than netplwiz. I’ll give GUI steps first, then exact commands for PowerShell if you prefer automation. I’ll also show the fallback (clear NGC) only if Settings refuses to remove the PIN.
Security reminder (read before you proceed)
  • Automatic sign‑in means anyone with physical access to the PC can open your account. Only enable this on a safe, private machine.
  • Keep a Windows recovery USB and your Microsoft password handy.
Option A — Recommended (remove PIN via Settings → use Autologon)
1) Remove the PIN (GUI)
  • Settings → Accounts → Sign‑in options → Windows Hello PIN → Remove.
  • You will be asked to confirm with your Microsoft account password. Complete that.
If the PIN removal succeeds, continue.
2) Download Autologon (one‑time)
  • Download “Autologon” from Microsoft Sysinternals (search “Autologon Sysinternals” or go to the Microsoft Sysinternals site).
  • Extract the ZIP to a folder (e.g. Downloads\Autologon).
3) Run Autologon as Administrator
  • Right‑click Autologon.exe → Run as administrator.
  • In the dialog:
    • Username: your Microsoft email address (the account you sign in with).
    • Domain: leave blank (or your PC name).
    • Password: your Microsoft account password.
  • Click Enable. You should get a confirmation that Autologon is enabled.
4) Test
  • Reboot your PC. It should sign in automatically to your Microsoft account.
To disable later: run Autologon.exe and click Disable.
Option B — Quick alternative using netplwiz (less secure)
1) Remove the PIN via Settings as above.
2) Press Win+R → type netplwiz → Enter.
3) Uncheck “Users must enter a user name and password.” Click Apply.
4) Enter your Microsoft account (email) and password when prompted. Click OK.
5) Reboot to test.
Note: netplwiz stores credentials in the registry (less secure than Autologon).
Option C — If Settings refuses to remove PIN (force clear NGC) — LAST RESORT
Only use this if the Remove button is not available or fails. This removes all Windows Hello PIN/biometric data on the machine; you’ll need to set up Windows Hello again if desired.
Run these commands in an elevated Command Prompt / PowerShell (Admin). They take ownership of the NGC folder and remove it:
takeown /F "C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\NGC" /R /D Y
icacls "C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\NGC" /grant Administrators:F /T /C
rd /s /q "C:\Windows\ServiceProfiles\LocalService\AppData\Local\Microsoft\NGC"
After that reboot, then set up Autologon (Option A) or netplwiz (Option B). Don’t run the NGC commands unless you must — only if Settings won’t remove the PIN.
Troubleshooting notes
  • If Autologon says it cannot enable: ensure you typed the correct Microsoft password and run Autologon as Administrator.
  • If automatic sign‑in fails after reboot for a Microsoft account, you may be prompted for network sign‑in or the account may need MFA — Autologon cannot bypass MFA prompts. In that case you can enable autologon but still might need to enter the MFA code after certain changes.
  • If you prefer, I can give the exact Autologon command‑line usage. Or I can walk you through the process step‑by‑step while you do it.
Which would you like to try now?
  • “Autologon (recommended)” — I’ll wait while you remove the PIN and run Autologon and will verify the result.
  • “netplwiz” — I’ll wait and verify.
  • “Clear NGC then Autologon” — I’ll give the exact commands and wait for you to confirm each step.
Tell me which and I’ll stand by.
 
I reinstalled Acronis and I'm waiting for it take a backup. Since its the first backup it will be the full version so it will take another 15 minutes. I'll reboot once its complete.
Don't post any further commands.
 
You must log in or register to reply here.