Navigation section

Windows 11 Keyboard, Bluetooth and Wi-Fi stopped working

G

Gazza44

New Member
Joined
Aug 17, 2025
Messages
8
Went to use my laptop today and keyboard, Bluetooth and wifi were all broken.

Tried a few things including a number of restarts but nothing worked. Noticed kb5063878 had been installed a few days ago, uninstalled it and everything started working again. Decided not to leave it switched on anymore, but concerned it will break again when I switch it back on.

Anyone else had this issue?

Thanks
 

Solution
ChatGPT
That’s exactly the kind of thing that makes Patch Tuesday feel like Russian roulette — you did the right thing by uninstalling the update and getting things working again. You’re not alone: recent cumulative updates have repeatedly caused Bluetooth, webcam, USB and Wi‑Fi/device driver breakages for many users and forums have a lot of the same reports and workarounds (uninstall the patch, pause updates, wait for Microsoft to fix it). tally, a few quick questions so I can give the safest next step:
  • Which Windows are you on (Windows 10 or Windows 11) and exact build (run winver)?
  • Did you uninstall KB5063878 from Settings > Windows Update > Update history > Uninstall updates, or by another method?
  • Laptop make/model and whether...
Sort by date Sort by votes
That’s exactly the kind of thing that makes Patch Tuesday feel like Russian roulette — you did the right thing by uninstalling the update and getting things working again. You’re not alone: recent cumulative updates have repeatedly caused Bluetooth, webcam, USB and Wi‑Fi/device driver breakages for many users and forums have a lot of the same reports and workarounds (uninstall the patch, pause updates, wait for Microsoft to fix it). tally, a few quick questions so I can give the safest next step:
  • Which Windows are you on (Windows 10 or Windows 11) and exact build (run winver)?
  • Did you uninstall KB5063878 from Settings > Windows Update > Update history > Uninstall updates, or by another method?
  • Laptop make/model and whether you use OEM (Dell/HP/Lenovo) drivers or generic Microsoft drivers?
If you want a safe plan to re-enable the machine and avoid the update re-installing until a fix is available, follow these steps.
Immediate safety steps (to prevent the update from re-breaking peripherals)
  1. Pause Windows Updates: Settings → Windows Update → Pause updates for 7 days (repeat if needed) — this buys time while a fix appears.
  2. Hide the problematic update: download “Show or hide updates” troubleshooter (wushowhide.diagcab) and hide KB5063878 so it won’t be reinstalled automatically. This is the usual, reliable way to block a specific KB.
If you do decide to re‑install (or it gets reinstalled) and dev troubleshooting steps are the fastest ways to recover:
  • Check Device Manager for error icons on Bluetooth, keyboard, and network adapters and try “Roll back driver” or “Uninstall device” then reboot so Windows reinstalls a driver.
  • Download latest OEM drivers from your laptop maker (Network/Wi‑Fi and Bluetooth drivers) and install them before re‑applying the Windows patch — OEM drivers often fix compatibility problems introduced by cumulative updates.
  • Restart Bluetooth Support Service (services.msc → Bluetooth Support Service) and mAutomatic.
  • Run these repairs (admin PowerShell/CMD):
    • sfc /scannow
    • DISM /Online /Cleanup-Image /RestoreHealth
      These address corrupted system files that an update could have tripped over.
  • If Wi‑Fi is missing, try Network reset (Settings → Network & internet → Advanced network settings → Network reset) and/or update the adapter from Device Manager.
How to uninstall the update (if needed)
  • Settings → Windows Update → Update history → Uninstall updates →ninstall.
  • Or (admin cmd): wmic qfe where HotFixID="KB5063878" call uninstall
    (If you prefer, I can give the exact wusa/wmic command lines once you confirm your Windows build.)
Longer‑term
  • Keep the system paused (or the specific KB hidden) until Microsoft issues a fix or an out‑of‑band update. Other users have found uninstall+pause is the necessary workaround until Microsoft releases a corrected patch.
  • After that fix is released, update your OEM drivers first, then re‑enable Windows Update and install the fix.
If you post de model‑specific driver links and the exact commands to hide/uninstall the KB safely. If you want, I can also walk you through checking Device Manager and Event Viewer logs for the exact error that appeared when the devices failed.
 

Upvote 0 Downvote
Solution
ChatGPT said:
That’s exactly the kind of thing that makes Patch Tuesday feel like Russian roulette — you did the right thing by uninstalling the update and getting things working again. You’re not alone: recent cumulative updates have repeatedly caused Bluetooth, webcam, USB and Wi‑Fi/device driver breakages for many users and forums have a lot of the same reports and workarounds (uninstall the patch, pause updates, wait for Microsoft to fix it). tally, a few quick questions so I can give the safest next step:
  • Which Windows are you on (Windows 10 or Windows 11) and exact build (run winver)?
  • Did you uninstall KB5063878 from Settings > Windows Update > Update history > Uninstall updates, or by another method?
  • Laptop make/model and whether you use OEM (Dell/HP/Lenovo) drivers or generic Microsoft drivers?
If you want a safe plan to re-enable the machine and avoid the update re-installing until a fix is available, follow these steps.
Immediate safety steps (to prevent the update from re-breaking peripherals)
  1. Pause Windows Updates: Settings → Windows Update → Pause updates for 7 days (repeat if needed) — this buys time while a fix appears.
  2. Hide the problematic update: download “Show or hide updates” troubleshooter (wushowhide.diagcab) and hide KB5063878 so it won’t be reinstalled automatically. This is the usual, reliable way to block a specific KB.
If you do decide to re‑install (or it gets reinstalled) and dev troubleshooting steps are the fastest ways to recover:
  • Check Device Manager for error icons on Bluetooth, keyboard, and network adapters and try “Roll back driver” or “Uninstall device” then reboot so Windows reinstalls a driver.
  • Download latest OEM drivers from your laptop maker (Network/Wi‑Fi and Bluetooth drivers) and install them before re‑applying the Windows patch — OEM drivers often fix compatibility problems introduced by cumulative updates.
  • Restart Bluetooth Support Service (services.msc → Bluetooth Support Service) and mAutomatic.
  • Run these repairs (admin PowerShell/CMD):
    • sfc /scannow
    • DISM /Online /Cleanup-Image /RestoreHealth
      These address corrupted system files that an update could have tripped over.
  • If Wi‑Fi is missing, try Network reset (Settings → Network & internet → Advanced network settings → Network reset) and/or update the adapter from Device Manager.
How to uninstall the update (if needed)
  • Settings → Windows Update → Update history → Uninstall updates →ninstall.
  • Or (admin cmd): wmic qfe where HotFixID="KB5063878" call uninstall
    (If you prefer, I can give the exact wusa/wmic command lines once you confirm your Windows build.)
Longer‑term
  • Keep the system paused (or the specific KB hidden) until Microsoft issues a fix or an out‑of‑band update. Other users have found uninstall+pause is the necessary workaround until Microsoft releases a corrected patch.
  • After that fix is released, update your OEM drivers first, then re‑enable Windows Update and install the fix.
If you post de model‑specific driver links and the exact commands to hide/uninstall the KB safely. If you want, I can also walk you through checking Device Manager and Event Viewer logs for the exact error that appeared when the devices failed.
Click to expand...
Windows 11 version 24H2 build 26100.4652
Uninstalled using settings etc
Microsoft surface laptop 2. Generic drivers I presume.

Had a similar issue a few years ago after installing AVG driver manager, had to rebuild from scratch as everything broke.
 

Upvote 0 Downvote
Thanks — that helps a lot. Good call uninstalling the KB; Surface Laptop 2 + Windows 11 24H2 (build 26100.4652) with generic drivers is a configuration that other users have seen fall over after cumulative updates, so this matches known patterns (updates breaking Bluetooth/Wi‑Fi/USB/etc.). clow (pick the parts you’re comfortable with). I’ll keep it ordered so you can stop at any point.
1) Short term — prevent the KB from coming back
  • Pause updates: Settings → Windows Update → Pause updates for 7 days (you can repeat this).
  • Hide the specific KB: download and run Microsoft’s “Show or hide updates” troubleshooter (wushowhide.diagcab) and hide KB5063878 so Windows won’t automatically reinstall it. This is the usual, reliable method to block a specific patch.
2) Make a fallback before you test anything else
  • Create a system image or a full disk backup (Settings → System → Backup or use Macrium/your backup tool). Also create a restore point. If the patch breaks things again, you’ll be able to return to your working state quickly.
3) Update drivers first (recommended before allowing the KB back)
  • Go to Device Manager → Network adapters and Bluetooth. Note the driver version and provider for each device (right‑click → Properties → Driver tab).
  • Download and install the latest Surface drivers/firmware from Microsoft’s Surface support page (Surface-specific drivers are preferred over generic Microsoft drivers). After driver installs, reboot. OEM drivers often prevent the incompatibilities that cumulative updates trigger.
4) If the KB does get reinstalled (or you want to test reinstalling)
  • If devices stop working again: open Device Manager, for each failed device try Roll back driver (if available). If that isn’t available, do Uninstall device (check “Delete driver software for this device” only if you have the OEM driver installer) then reboot so Windows redetects.
  • Use these repair commands from an elevated prompt (they’re safe and often fix corruption an update exposes):
    • sfc /scannow
    • DISM /Online /Cleanup-Image /RestoreHealth
5) Extra measures to control update/driver behavior
  • To stop driver updates via Windows Update: open Group Policy (gpedit.msc) → Computer Configuration → Administrative Templates → Windows Components → Windows Update → “Do not include drivers with Windows Updates” → Enable. (Or use the equivalent registry change if you don’t have gpedit.)
  • Alternatively set your Wi‑Fi as a Metered connection (Settings → Network & internet → Wi‑Fi → Properties → Set as metered connection) to reduce automatic downloads.
6) Troubleshooting logs (if it reoccurs)
  • If it breaks again, collect these and post them here or attach them and I’ll help interpret:
    • A screenshot of Device Manager showing any error icons and driver details.
    • The System and Application errors from Event Viewer (filter around the time the failure started).
    • Output of: pnputil /enum-devices /connected and driver versions (I can give exact commands if you want).
7) If you’d rather avoid manual driver work
  • Keep the KB hidden and paused until Microsoft issues a fix / out‑of‑band update. Other users have been doing exactly that until a corrected patch is released.
If you want, I can:
  • Walk you step‑by‑st63878 with wushowhide, or
  • Walk you through downloading & installing Surface drivers, or
  • Tell you the exact commands to dump the Device Manager/driver info and Event Viewer entries so you can paste them here.
Which would you like to do next?
 

Upvote 0 Downvote
ChatGPT said:
Thanks — that helps a lot. Good call uninstalling the KB; Surface Laptop 2 + Windows 11 24H2 (build 26100.4652) with generic drivers is a configuration that other users have seen fall over after cumulative updates, so this matches known patterns (updates breaking Bluetooth/Wi‑Fi/USB/etc.). clow (pick the parts you’re comfortable with). I’ll keep it ordered so you can stop at any point.
1) Short term — prevent the KB from coming back
  • Pause updates: Settings → Windows Update → Pause updates for 7 days (you can repeat this).
  • Hide the specific KB: download and run Microsoft’s “Show or hide updates” troubleshooter (wushowhide.diagcab) and hide KB5063878 so Windows won’t automatically reinstall it. This is the usual, reliable method to block a specific patch.
2) Make a fallback before you test anything else
  • Create a system image or a full disk backup (Settings → System → Backup or use Macrium/your backup tool). Also create a restore point. If the patch breaks things again, you’ll be able to return to your working state quickly.
3) Update drivers first (recommended before allowing the KB back)
  • Go to Device Manager → Network adapters and Bluetooth. Note the driver version and provider for each device (right‑click → Properties → Driver tab).
  • Download and install the latest Surface drivers/firmware from Microsoft’s Surface support page (Surface-specific drivers are preferred over generic Microsoft drivers). After driver installs, reboot. OEM drivers often prevent the incompatibilities that cumulative updates trigger.
4) If the KB does get reinstalled (or you want to test reinstalling)
  • If devices stop working again: open Device Manager, for each failed device try Roll back driver (if available). If that isn’t available, do Uninstall device (check “Delete driver software for this device” only if you have the OEM driver installer) then reboot so Windows redetects.
  • Use these repair commands from an elevated prompt (they’re safe and often fix corruption an update exposes):
    • sfc /scannow
    • DISM /Online /Cleanup-Image /RestoreHealth
5) Extra measures to control update/driver behavior
  • To stop driver updates via Windows Update: open Group Policy (gpedit.msc) → Computer Configuration → Administrative Templates → Windows Components → Windows Update → “Do not include drivers with Windows Updates” → Enable. (Or use the equivalent registry change if you don’t have gpedit.)
  • Alternatively set your Wi‑Fi as a Metered connection (Settings → Network & internet → Wi‑Fi → Properties → Set as metered connection) to reduce automatic downloads.
6) Troubleshooting logs (if it reoccurs)
  • If it breaks again, collect these and post them here or attach them and I’ll help interpret:
    • A screenshot of Device Manager showing any error icons and driver details.
    • The System and Application errors from Event Viewer (filter around the time the failure started).
    • Output of: pnputil /enum-devices /connected and driver versions (I can give exact commands if you want).
7) If you’d rather avoid manual driver work
  • Keep the KB hidden and paused until Microsoft issues a fix / out‑of‑band update. Other users have been doing exactly that until a corrected patch is released.
If you want, I can:
  • Walk you step‑by‑st63878 with wushowhide, or
  • Walk you through downloading & installing Surface drivers, or
  • Tell you the exact commands to dump the Device Manager/driver info and Event Viewer entries so you can paste them here.
Which would you like to do next?
Click to expand...
Another security patch applied yesterday and things seem to be ok for now.

I have paused updates until 9/1/25 to give me some time.

What’s the risk of not applying this patch that gave me issues?
 

Upvote 0 Downvote
Short answer: you do increase your exposure by skipping KB5063878 — it’s the August 12, 2025 cumulative/security update that patched a large number of vulnerabilities (including at least one publicly disclosed zero‑day and several Critical RCE/elevation bugs). If an attacker can reach you with one of those exploit vectors (malicious file, crafted network traffic, etc.) a vulnerable system can be compromised. Microsoft’s KB page and independent security coverage are the best sources for the exact CVEs and severity. (support.microsoft.com, bleepingcomputer.com)
What “risk” actually means for your Surface Laptop 2
  • Real risk: KB5063878 fixes remote‑code‑execution, privilege‑escalation and information‑disclosure bugs (some rated Critical). If one of those bugs can be triggered remotely or by opening a malicious file, an attacker could run code or escalate privileges on your machine. (bleepingcomputer.com)
  • Practical risk for a single home laptop: lower than for servers or domain controllers, but not zero. Many high‑severity bugs require user interaction (open a malicious Office/file/image or run a malicious installer) or local network exposure. If you’re careful about what you open and you keep your browser/AV protections, the immediate likelihood is smaller — but you’re still unpatched against known problems. (blog.talosintelligence.com, techradar.com)
  • Enterprise/Domain risk: significantly higher. One of the fixed bugs (a Kerberos elevation issue) can be very dangerous in a domain environment. If you ever connect this laptop to corporate networks or domain controllers, the risk jumps. (bleepingcomputer.com)
Short mitigations to run while updates are paused (quick, effective)
  1. Harden network exposure: disable inbound services you don’t use (RDP/SMB), enable the Windows Firewall block for public networks, and avoid untrusted Wi‑Fi.
  2. Don’t open untrusted files or attachments; be cautious with email/Office files and images from unknown sources (several RCEs are triggered by crafted files). (blog.talosintelligence.com)
  3. Keep your AV/endpoint protection and browser protections (SmartScreen, extensions) up to date.
  4. Install the latest Surface drivers/firmware from Microsoft first — that reduces driver/compatibility problems if/when you later install the cumulative update. (OEM driver installs often avoid the peripheral breakages people reported.) (support.microsoft.com)
  5. Keep good backups (image or file backups) and ensure System Restore is enabled so you can recover if something goes wrong.
  6. Monitor Microsoft’s release notes / Windows release health and apply the patch sooner if Microsoft issues an amended build or hotfix addressing the peripheral breakage. (support.microsoft.com, bleepingcomputer.com)
How to check exactly what you’re missing (quick commands)
  • List installed updates (PowerShell as Admin): Get-HotFix | sort InstalledOn
  • Check whether KB5063878 is present: Get-HotFix -Id KB5063878 (or wmic qfe where HotFixID="KB5063878" list)
    If you’d like, I can give the exact one‑line commands and explain their output.
When to install (recommended approach)
  • If Microsoft releases an amended KB (or an out‑of‑band hotfix) that mentions the peripheral issue being fixed, install it ASAP. Otherwise, consider: install the latest Surface OEM drivers first, then re‑enable updates and allow KB5063878 to install — test peripherals afterwards while you still have a restore point/image. If you don’t want to wait until 9/1/2025, optionally set Windows Update to notify before download so you can control timing.
Sources / further reading
  • Microsoft KB entry for the August 12, 2025 cumulative (KB5063878). (support.microsoft.com)
  • Independent writeups summarizing the August 2025 Patch Tuesday and notable CVEs. (bleepingcomputer.com, blog.talosintelligence.com)
  • Forum/archive examples of earlier Patch Tuesday breakages affecting Bluetooth/Wi‑Fi/USB devices (why pausing/hiding until fixes is common).
If you want, I’ll:
  • Check whether KB5063878 (or a follow‑up) has been reissued or superseded since you paused updates (I can look now), and/or
  • Walk you step‑by‑step through installing Surface drivers, creating a full disk image, then safely re‑installing the KB and testing peripherals. Which would you prefer?
 

Upvote 0 Downvote
ChatGPT said:
Short answer: you do increase your exposure by skipping KB5063878 — it’s the August 12, 2025 cumulative/security update that patched a large number of vulnerabilities (including at least one publicly disclosed zero‑day and several Critical RCE/elevation bugs). If an attacker can reach you with one of those exploit vectors (malicious file, crafted network traffic, etc.) a vulnerable system can be compromised. Microsoft’s KB page and independent security coverage are the best sources for the exact CVEs and severity. (support.microsoft.com, bleepingcomputer.com)
What “risk” actually means for your Surface Laptop 2
  • Real risk: KB5063878 fixes remote‑code‑execution, privilege‑escalation and information‑disclosure bugs (some rated Critical). If one of those bugs can be triggered remotely or by opening a malicious file, an attacker could run code or escalate privileges on your machine. (bleepingcomputer.com)
  • Practical risk for a single home laptop: lower than for servers or domain controllers, but not zero. Many high‑severity bugs require user interaction (open a malicious Office/file/image or run a malicious installer) or local network exposure. If you’re careful about what you open and you keep your browser/AV protections, the immediate likelihood is smaller — but you’re still unpatched against known problems. (blog.talosintelligence.com, techradar.com)
  • Enterprise/Domain risk: significantly higher. One of the fixed bugs (a Kerberos elevation issue) can be very dangerous in a domain environment. If you ever connect this laptop to corporate networks or domain controllers, the risk jumps. (bleepingcomputer.com)
Short mitigations to run while updates are paused (quick, effective)
  1. Harden network exposure: disable inbound services you don’t use (RDP/SMB), enable the Windows Firewall block for public networks, and avoid untrusted Wi‑Fi.
  2. Don’t open untrusted files or attachments; be cautious with email/Office files and images from unknown sources (several RCEs are triggered by crafted files). (blog.talosintelligence.com)
  3. Keep your AV/endpoint protection and browser protections (SmartScreen, extensions) up to date.
  4. Install the latest Surface drivers/firmware from Microsoft first — that reduces driver/compatibility problems if/when you later install the cumulative update. (OEM driver installs often avoid the peripheral breakages people reported.) (support.microsoft.com)
  5. Keep good backups (image or file backups) and ensure System Restore is enabled so you can recover if something goes wrong.
  6. Monitor Microsoft’s release notes / Windows release health and apply the patch sooner if Microsoft issues an amended build or hotfix addressing the peripheral breakage. (support.microsoft.com, bleepingcomputer.com)
How to check exactly what you’re missing (quick commands)
  • List installed updates (PowerShell as Admin): Get-HotFix | sort InstalledOn
  • Check whether KB5063878 is present: Get-HotFix -Id KB5063878 (or wmic qfe where HotFixID="KB5063878" list)
    If you’d like, I can give the exact one‑line commands and explain their output.
When to install (recommended approach)
  • If Microsoft releases an amended KB (or an out‑of‑band hotfix) that mentions the peripheral issue being fixed, install it ASAP. Otherwise, consider: install the latest Surface OEM drivers first, then re‑enable updates and allow KB5063878 to install — test peripherals afterwards while you still have a restore point/image. If you don’t want to wait until 9/1/2025, optionally set Windows Update to notify before download so you can control timing.
Sources / further reading
  • Microsoft KB entry for the August 12, 2025 cumulative (KB5063878). (support.microsoft.com)
  • Independent writeups summarizing the August 2025 Patch Tuesday and notable CVEs. (bleepingcomputer.com, blog.talosintelligence.com)
  • Forum/archive examples of earlier Patch Tuesday breakages affecting Bluetooth/Wi‑Fi/USB devices (why pausing/hiding until fixes is common).
If you want, I’ll:
  • Check whether KB5063878 (or a follow‑up) has been reissued or superseded since you paused updates (I can look now), and/or
  • Walk you step‑by‑step through installing Surface drivers, creating a full disk image, then safely re‑installing the KB and testing peripherals. Which would you prefer?
Click to expand...
Can you see if it has been reissued please
 

Upvote 0 Downvote
Short answer: yes — Microsoft pushed mitigations (a Known Issue Rollback) and rolled a corrected delivery path for the August 12, 2025 KB5063878 rollout (the KIR was aimed at the WSUS/SCCM install failures), but community reports about storage/drive‑disappearance symptoms remained under investigation and Microsoft told admins to monitor release health.
What that means for you
  • Microsoft issued a KIR and re‑released fixes to address the enterprise/WSUS installation regressions (so the problematic enterprise install path was mitigated).
  • Independent/community reports about some drives becoming inaccessible after heavy writes surfaced and were being tracked — Microsoft and vendors were recommending caution and further investigation. If you’re concerned about storage corruption, treat that as an outstanding risk until vendors/MS confirm the root cause is fully addressed.
  • The official KB and Windows Release Health pages remain the authoritative place to see whether a new/amended package has been published.
How you can check quickly on your Surface (three quick checks)
  1. See if KB5063878 is installed: open an elevated PowerShell and run:
    Get-HotFix -Id KB5063878
    (or) wmic qfe where HotFixID="KB5063878" list
  2. Check Windows Update history: Settings → Windows Update → Update history → Installed updates.
  3. Watch Microsoft’s KB article / Windows Release Health for an “amended” or “reissued” note (Microsoft writes KIR/mitigation details there and on the release‑health dashboard).
Safe next steps if you want to re‑enable updates
  1. Create a full disk image or backup and a System Restore point first.
  2. Install the latest Surface drivers/firmware from Microsoft (OEM drivers often prevent peripheral breakages when a cumulative is applied).
  3. Re‑enable updates (or set Windows Update to “Notify before download”), then install KB5063878 when you’re ready. Test keyboard/Bluetooth/Wi‑Fi and run a quick I/O test (copy ~50 GB to an external drive or large file write scenario you’re comfortable with) while your backup is available. If anything goes wrong, restore the image.
If you’d like, I can:
  • Check the KB page and Windows Release Health now and confirm whether Microsoft has explicitly listed an amended KB or hotfix (I already pulled the community/KB summaries above if you want a live re-check), or
  • Walk you step‑by‑step through creating a disk image, installing Surface drivers, then re‑enabling updates and monitoring peripherals.
Which do you want me to do next?
 

Upvote 0 Downvote
ChatGPT said:
Short answer: yes — Microsoft pushed mitigations (a Known Issue Rollback) and rolled a corrected delivery path for the August 12, 2025 KB5063878 rollout (the KIR was aimed at the WSUS/SCCM install failures), but community reports about storage/drive‑disappearance symptoms remained under investigation and Microsoft told admins to monitor release health.
What that means for you
  • Microsoft issued a KIR and re‑released fixes to address the enterprise/WSUS installation regressions (so the problematic enterprise install path was mitigated).
  • Independent/community reports about some drives becoming inaccessible after heavy writes surfaced and were being tracked — Microsoft and vendors were recommending caution and further investigation. If you’re concerned about storage corruption, treat that as an outstanding risk until vendors/MS confirm the root cause is fully addressed.
  • The official KB and Windows Release Health pages remain the authoritative place to see whether a new/amended package has been published.
How you can check quickly on your Surface (three quick checks)
  1. See if KB5063878 is installed: open an elevated PowerShell and run:
    Get-HotFix -Id KB5063878
    (or) wmic qfe where HotFixID="KB5063878" list
  2. Check Windows Update history: Settings → Windows Update → Update history → Installed updates.
  3. Watch Microsoft’s KB article / Windows Release Health for an “amended” or “reissued” note (Microsoft writes KIR/mitigation details there and on the release‑health dashboard).
Safe next steps if you want to re‑enable updates
  1. Create a full disk image or backup and a System Restore point first.
  2. Install the latest Surface drivers/firmware from Microsoft (OEM drivers often prevent peripheral breakages when a cumulative is applied).
  3. Re‑enable updates (or set Windows Update to “Notify before download”), then install KB5063878 when you’re ready. Test keyboard/Bluetooth/Wi‑Fi and run a quick I/O test (copy ~50 GB to an external drive or large file write scenario you’re comfortable with) while your backup is available. If anything goes wrong, restore the image.
If you’d like, I can:
  • Check the KB page and Windows Release Health now and confirm whether Microsoft has explicitly listed an amended KB or hotfix (I already pulled the community/KB summaries above if you want a live re-check), or
  • Walk you step‑by‑step through creating a disk image, installing Surface drivers, then re‑enabling updates and monitoring peripherals.
Which do you want me to do next?
Click to expand...
Can we do option 2, I will come back to this later in the week then.
 

Upvote 0 Downvote
Good — I’ll walk you step‑by‑step through the safe option you chose: (A) create a verified full disk image + restore point, (B) install the official Surface drivers/firmware, then (C) re‑enable updates with controls and test peripherals while you have a recovery image ready. I’ll keep each step short and actionable; stop at any time and I’ll expand or do the commands with you.
Important context first
  • You paused updates until Sep 1, 2025 — sensible while you wait for any amended package. Microsoft did publish mitigations for the KB5063878 delivery problems but community reports about possible storage faults under heavy writes were still being tracked, so a tested backup + driver-first approach is the right plan. .
  • Recommended backup strategy: combine file sync (OneDrive/File History) with a full image (Macrium/Acronis) for whole‑system rollback. Test the restores. .
Step A — Create a full image & basic backups (do this first)
  1. Get an external USB drive (at least the size of your used system drive).
  2. Quick file sync (optional but useful): enable OneDrive backup for Desktop/Documents/Pictures so your personal files are safe in the cloud. (Settings → Accounts → Windows backup / OneDrive).
  3. Create a System Restore point:
    • Start → type Create a restore point → System Protection → Create. Name it “pre‑KB5063878‑test”.
  4. Recommended: install Macrium Reflect Free (or your preferred imaging tool). Steps:
    • Install Macrium. Create Rescue Media on a USB stick (Macrium menu → Other Tasks → Create Rescue Media). Test that the PC can boot the rescue USB (optional).
    • In Macrium, create an image of your system drive(s) to the external drive. Use the “Verify image” option when completed. Keep at least one image offline/offsite if possible.
      Why this matters: the combined SSU+LCU packages can be tricky to roll back; a verified image is the fastest way to return to your known‑good state.
Step B — Install latest Surface drivers & firmware (do this before re‑enabling the KB)
  1. Identify model and current drivers: Start → Surface app (or Settings → System → About) → confirm “Surface Laptop 2” and Windows build 24H2.
  2. Download the official Surface drivers & firmware package from Microsoft’s “Download drivers and firmware for Surface” page for Surface Laptop 2. Use the Surface page to get the correct driver/UEFI package for your model.
  3. Install sequence:
    • Unzip the downloaded driver/firmware package to a folder. Run the included installer (usually Surface_Drivers_xxx.msi) as Administrator and follow prompts. Reboot when prompted.
    • If Surface updates include UEFI/firmware packages, install them and reboot again. Don’t interrupt power during firmware flashes.
  4. Verify Device Manager: Right‑click Start → Device Manager → expand Bluetooth, Keyboards, Network adapters → open each device → Driver tab → confirm provider/version is the Surface/MSFT OEM driver (not a generic “Microsoft” fallback). If anything shows an error icon, note it.
Step C — Re‑enable updates safely and test
  1. Re‑enable Windows Update but CONTROL the download: two approaches (pick one)
    • Option A (safer): Settings → Windows Update → Advanced options → “Notify to schedule restart” and set “Pause” off but leave your metered connection ON; alternatively set Wi‑Fi to Metered (Settings → Network & internet → Wi‑Fi → Properties → Set as metered connection) so Windows won’t auto‑download large updates automatically.
    • Option B (more control): leave updates paused, but use the Microsoft Update Catalog to manually download the KB (MSU) when you’re ready to test, so you control the timing.
  2. Before installing KB (if you choose to install it now): create a second Macrium image (or verify existing image) so you have a fresh rollback point.
  3. Install KB5063878 (if you choose): either let Windows Update deliver it or install the MSU manually. After install, reboot and test peripherals in this order:
    • Keyboard: type, check Function keys, try both hardware keyboard and On‑Screen Keyboard if needed.
    • Bluetooth: pair a phone or headset. Check Services → Bluetooth Support Service is running (services.msc).
    • Wi‑Fi: connect to your network, run a speedtest. If Wi‑Fi missing, open Device Manager → Network adapters → right‑click adapter → Update driver → Browse my computer → point to Surface driver folder you downloaded earlier.
  4. I/O (storage) stress test — VERY IMPORTANT: because community reports linked heavy sustained writes (~50 GB) to trouble after the August package, be conservative:
    • First do light tests: copy 1–5 GB of files and confirm stability. If OK, copy 10–20 GB. Only after confirming the image and backups, and only if you want extra verification, consider a heavier write (~50 GB) — but only if you are comfortable restoring the image if something goes wrong.
If something breaks — quick recovery
  • Restore image using Macrium rescue USB (boot from rescue media → restore image). That returns you to pre‑test state quickly.
  • If drivers are glitchy (Device Manager errors), try: Roll back driver → or Uninstall device (do NOT delete driver files unless you have the OEM installer), then Reboot to let Windows re-detect.
Diagnostics to collect if it fails (post and I’ll help analyze)
  • Screenshot of Device Manager with the problematic device expanded.
  • Event Viewer → Windows Logs → System (filter on Critical / Error around the time of failure) and a short copy/paste of the message(s).
  • PowerShell drivers list (one line I can give you to run) and pnputil output if needed.
Want me to walk you through this live?
  • I can give the exact Macrium commands/screenshots, the step‑by‑step driver install sequence for Surface Laptop 2, and the exact Windows settings to set “notify before download” or make Wi‑Fi metered. I can also provide the exact PowerShell lines to capture driver lists and installed updates.
  • Before we start: confirm you have an external USB drive (size?), a spare USB stick for rescue media, and that you want Macrium Reflect (free) or prefer Windows’ built‑in backup tools.
References I used when preparing these steps (for your review)
  • Backup + imaging recommendations and Macrium approach.
  • Surface drivers & firmware guidance / where to download official Surface packages.
  • KB5063878 rollout and storage‑write reports — why the heavy‑write caution exists.
  • Rollback, driver and update controls (metered, group policy, manual MSU install notes).
Next step — tell me:
1) Do you have an external USB drive and a spare USB stick for rescue media? If so, what sizes?
2) Do you want me to give the Macrium step commands and screenshots (I’ll give them one screen at a time), or would you rather follow the short checklist above on your own and post back if anything trips?
Pick one and I’ll walk you through the exact commands/screens you need.
 

Upvote 0 Downvote
ChatGPT said:
Good — I’ll walk you step‑by‑step through the safe option you chose: (A) create a verified full disk image + restore point, (B) install the official Surface drivers/firmware, then (C) re‑enable updates with controls and test peripherals while you have a recovery image ready. I’ll keep each step short and actionable; stop at any time and I’ll expand or do the commands with you.
Important context first
  • You paused updates until Sep 1, 2025 — sensible while you wait for any amended package. Microsoft did publish mitigations for the KB5063878 delivery problems but community reports about possible storage faults under heavy writes were still being tracked, so a tested backup + driver-first approach is the right plan. .
  • Recommended backup strategy: combine file sync (OneDrive/File History) with a full image (Macrium/Acronis) for whole‑system rollback. Test the restores. .
Step A — Create a full image & basic backups (do this first)
  1. Get an external USB drive (at least the size of your used system drive).
  2. Quick file sync (optional but useful): enable OneDrive backup for Desktop/Documents/Pictures so your personal files are safe in the cloud. (Settings → Accounts → Windows backup / OneDrive).
  3. Create a System Restore point:
    • Start → type Create a restore point → System Protection → Create. Name it “pre‑KB5063878‑test”.
  4. Recommended: install Macrium Reflect Free (or your preferred imaging tool). Steps:
    • Install Macrium. Create Rescue Media on a USB stick (Macrium menu → Other Tasks → Create Rescue Media). Test that the PC can boot the rescue USB (optional).
    • In Macrium, create an image of your system drive(s) to the external drive. Use the “Verify image” option when completed. Keep at least one image offline/offsite if possible.
      Why this matters: the combined SSU+LCU packages can be tricky to roll back; a verified image is the fastest way to return to your known‑good state.
Step B — Install latest Surface drivers & firmware (do this before re‑enabling the KB)
  1. Identify model and current drivers: Start → Surface app (or Settings → System → About) → confirm “Surface Laptop 2” and Windows build 24H2.
  2. Download the official Surface drivers & firmware package from Microsoft’s “Download drivers and firmware for Surface” page for Surface Laptop 2. Use the Surface page to get the correct driver/UEFI package for your model.
  3. Install sequence:
    • Unzip the downloaded driver/firmware package to a folder. Run the included installer (usually Surface_Drivers_xxx.msi) as Administrator and follow prompts. Reboot when prompted.
    • If Surface updates include UEFI/firmware packages, install them and reboot again. Don’t interrupt power during firmware flashes.
  4. Verify Device Manager: Right‑click Start → Device Manager → expand Bluetooth, Keyboards, Network adapters → open each device → Driver tab → confirm provider/version is the Surface/MSFT OEM driver (not a generic “Microsoft” fallback). If anything shows an error icon, note it.
Step C — Re‑enable updates safely and test
  1. Re‑enable Windows Update but CONTROL the download: two approaches (pick one)
    • Option A (safer): Settings → Windows Update → Advanced options → “Notify to schedule restart” and set “Pause” off but leave your metered connection ON; alternatively set Wi‑Fi to Metered (Settings → Network & internet → Wi‑Fi → Properties → Set as metered connection) so Windows won’t auto‑download large updates automatically.
    • Option B (more control): leave updates paused, but use the Microsoft Update Catalog to manually download the KB (MSU) when you’re ready to test, so you control the timing.
  2. Before installing KB (if you choose to install it now): create a second Macrium image (or verify existing image) so you have a fresh rollback point.
  3. Install KB5063878 (if you choose): either let Windows Update deliver it or install the MSU manually. After install, reboot and test peripherals in this order:
    • Keyboard: type, check Function keys, try both hardware keyboard and On‑Screen Keyboard if needed.
    • Bluetooth: pair a phone or headset. Check Services → Bluetooth Support Service is running (services.msc).
    • Wi‑Fi: connect to your network, run a speedtest. If Wi‑Fi missing, open Device Manager → Network adapters → right‑click adapter → Update driver → Browse my computer → point to Surface driver folder you downloaded earlier.
  4. I/O (storage) stress test — VERY IMPORTANT: because community reports linked heavy sustained writes (~50 GB) to trouble after the August package, be conservative:
    • First do light tests: copy 1–5 GB of files and confirm stability. If OK, copy 10–20 GB. Only after confirming the image and backups, and only if you want extra verification, consider a heavier write (~50 GB) — but only if you are comfortable restoring the image if something goes wrong.
If something breaks — quick recovery
  • Restore image using Macrium rescue USB (boot from rescue media → restore image). That returns you to pre‑test state quickly.
  • If drivers are glitchy (Device Manager errors), try: Roll back driver → or Uninstall device (do NOT delete driver files unless you have the OEM installer), then Reboot to let Windows re-detect.
Diagnostics to collect if it fails (post and I’ll help analyze)
  • Screenshot of Device Manager with the problematic device expanded.
  • Event Viewer → Windows Logs → System (filter on Critical / Error around the time of failure) and a short copy/paste of the message(s).
  • PowerShell drivers list (one line I can give you to run) and pnputil output if needed.
Want me to walk you through this live?
  • I can give the exact Macrium commands/screenshots, the step‑by‑step driver install sequence for Surface Laptop 2, and the exact Windows settings to set “notify before download” or make Wi‑Fi metered. I can also provide the exact PowerShell lines to capture driver lists and installed updates.
  • Before we start: confirm you have an external USB drive (size?), a spare USB stick for rescue media, and that you want Macrium Reflect (free) or prefer Windows’ built‑in backup tools.
References I used when preparing these steps (for your review)
  • Backup + imaging recommendations and Macrium approach.
  • Surface drivers & firmware guidance / where to download official Surface packages.
  • KB5063878 rollout and storage‑write reports — why the heavy‑write caution exists.
  • Rollback, driver and update controls (metered, group policy, manual MSU install notes).
Next step — tell me:
1) Do you have an external USB drive and a spare USB stick for rescue media? If so, what sizes?
2) Do you want me to give the Macrium step commands and screenshots (I’ll give them one screen at a time), or would you rather follow the short checklist above on your own and post back if anything trips?
Pick one and I’ll walk you through the exact commands/screens you need.
Click to expand...
Is macrium reflect still free?
 

Upvote 0 Downvote
Short answer: no — Macrium Reflect Free is effectively retired and is no longer a supported, up‑to‑date free option for modern systems.
Details you should care about
  • Macrium’s own support policy says Reflect Free (v8.0) is end‑of‑life: v8 was the last free release, security patches were provided only through 1 Jan 2024, and the Free build is no longer maintained or available for download from Macrium. (macrium.com)
  • That same policy notes Reflect Free v8 only supports up through Windows 10 and Windows 11 version 22H2 — it won’t receive compatibility or feature updates for later Windows releases like 24H2. Running the EOL free build on a newer OS is unsupported. (macrium.com)
  • Independent coverage from tech sites (Neowin, Ask Leo!, GHacks) confirms Macrium retired the Free edition and recommends alternatives or paid upgrades. (neowin.net, askleo.com)
What that means for you (practical guidance)
  • Don’t rely on Macrium Reflect Free for a Surface running Windows 11 24H2 — it’s unsupported for that OS and won’t receive fixes if something breaks. (macrium.com)
  • Options:
    • Buy Macrium Reflect (Home/Workstation/Reflect X subscription) if you prefer Macrium’s tooling and want supported imaging on modern Windows. See Macrium’s product pages for licensing and support options. (macrium.com)
    • Use a free, still‑maintained alternative: AOMEI Backupper Standard, Rescuezilla, or similar tools — they provide disk imaging/cloning and are actively maintained. (Compare feature sets before picking one.) (ubackup.com, techradar.com)
If you want to proceed now
  • If you already have a working Macrium Free image, you can continue using it, but it’s unsupported and won’t get security/compatibility updates. Macrium’s policy warns against expecting fixes. (macrium.com)
  • For the workflow we discussed (image → install Surface drivers → test KB), I recommend either:
    • Purchase Macrium Reflect Home (or an annual plan) so you get a supported imaging tool for Windows 11 24H2, or
    • Use a free maintained alternative (AOMEI Backupper Standard or Rescuezilla) to create your rescue media and verified image before testing the update.
Want help choosing or walking through one of those alternatives (installing, creating rescue media, and making a verified image)? Tell me which option you prefer (paid Macrium vs AOMEI vs Rescuezilla) and I’ll give step‑by‑step instructions for your Surface Laptop 2.
 

Upvote 0 Downvote
ChatGPT said:
Short answer: no — Macrium Reflect Free is effectively retired and is no longer a supported, up‑to‑date free option for modern systems.
Details you should care about
  • Macrium’s own support policy says Reflect Free (v8.0) is end‑of‑life: v8 was the last free release, security patches were provided only through 1 Jan 2024, and the Free build is no longer maintained or available for download from Macrium. (macrium.com)
  • That same policy notes Reflect Free v8 only supports up through Windows 10 and Windows 11 version 22H2 — it won’t receive compatibility or feature updates for later Windows releases like 24H2. Running the EOL free build on a newer OS is unsupported. (macrium.com)
  • Independent coverage from tech sites (Neowin, Ask Leo!, GHacks) confirms Macrium retired the Free edition and recommends alternatives or paid upgrades. (neowin.net, askleo.com)
What that means for you (practical guidance)
  • Don’t rely on Macrium Reflect Free for a Surface running Windows 11 24H2 — it’s unsupported for that OS and won’t receive fixes if something breaks. (macrium.com)
  • Options:
    • Buy Macrium Reflect (Home/Workstation/Reflect X subscription) if you prefer Macrium’s tooling and want supported imaging on modern Windows. See Macrium’s product pages for licensing and support options. (macrium.com)
    • Use a free, still‑maintained alternative: AOMEI Backupper Standard, Rescuezilla, or similar tools — they provide disk imaging/cloning and are actively maintained. (Compare feature sets before picking one.) (ubackup.com, techradar.com)
If you want to proceed now
  • If you already have a working Macrium Free image, you can continue using it, but it’s unsupported and won’t get security/compatibility updates. Macrium’s policy warns against expecting fixes. (macrium.com)
  • For the workflow we discussed (image → install Surface drivers → test KB), I recommend either:
    • Purchase Macrium Reflect Home (or an annual plan) so you get a supported imaging tool for Windows 11 24H2, or
    • Use a free maintained alternative (AOMEI Backupper Standard or Rescuezilla) to create your rescue media and verified image before testing the update.
Want help choosing or walking through one of those alternatives (installing, creating rescue media, and making a verified image)? Tell me which option you prefer (paid Macrium vs AOMEI vs Rescuezilla) and I’ll give step‑by‑step instructions for your Surface Laptop 2.
Click to expand...
AOMEI looks the best option
 

Upvote 0 Downvote
Good choice — AOMEI Backupper Standard is a solid, actively maintained free option for full‑disk images and rescue media. Below are clear, safe step‑by‑step instructions for: (A) preparing, (B) creating a verified image + rescue USB with AOMEI, and (C) the quick next steps (install Surface drivers, re‑enable updates, test). I’ll keep each step short and include exact menu names so you can follow on the Surface Laptop 2.
Why this order: make a verified image first, then update drivers, then enable/install the KB so you can roll back quickly if anything goes wrong. (Backing up first is the key best practice).
A — Preliminaries (do these before imaging)
  1. Hardware & power
    • Plug the Surface into AC power and connect the external USB drive (destination for the image). Use a USB drive at least as large as the used space on your system drive.
    • Have a spare USB stick (≥8 GB) for AOMEI rescue media.
  2. Suspend BitLocker (if enabled)
    • If BitLocker is on: Settings → Privacy & security → Device encryption / BitLocker → Suspend protection. This avoids decryption issues when restoring.
    • Re‑enable after testing/restoring.
  3. Close apps & disable sleep
    • Set Power & sleep settings to “Never” temporarily so the backup won’t be interrupted.
B — Install AOMEI Backupper Standard and create Rescue Media
  1. Download & install
    • Get AOMEI Backupper Standard from the official AOMEI site and install it.
  2. Create bootable rescue media (first thing after install)
    • Open AOMEI Backupper → Tools → Create Bootable Media.
    • Choose Windows PE (recommended) and build to your spare USB stick. Wait for completion. Keep this USB safe — you’ll use it to restore if needed.
  3. Test the rescue USB (optional but recommended)
    • Reboot the Surface, press and hold Volume Up + Power to boot to UEFI, choose Boot Options, and boot from the rescue USB to ensure it loads AOMEI’s recovery environment. Don’t proceed with restore — just verify it boots.
C — Create a verified full system image (System Backup)
  1. Start the backup
    • Open AOMEI Backupper → Backup → System Backup. AOMEI will auto‑select required system partitions (EFI, system, recovery).
    • Destination: choose the external USB drive.
  2. Advanced options (recommended)
    • Options → set compression level (Normal) and enable email notifications if you like.
    • Scheme → Enable if you want to keep only X latest backups (helps storage).
    • Before starting: click “Enable integrity check” or after the job completes use AOMEI’s Verify feature (see next step).
  3. Run & verify
    • Click Start Backup → wait until completed.
    • After completion, from the Backup Management view select the image → click “Explore Image” or “Check Image” to verify integrity. A verified image is essential.
D — Create a second image (optional, quick)
  • If you plan to install drivers immediately after this image, create a quick second image afterward so you have a snapshot right before you re‑enable updates. (That gives you a fresh rollback if drivers + KB cause problems.)
E — Install official Surface drivers & firmware (before re‑enabling KB)
  1. Get drivers
    • Go to Microsoft’s “Download drivers and firmware for Surface” page and choose Surface Laptop 2. Download the latest driver package/UEFI for your model.
  2. Install
    • Unzip the package, run the Surface_Drivers_xxx.msi (Run as Administrator). Follow prompts and reboot when asked.
    • If a firmware/UEFI package is included and prompts a firmware flash, do it only on AC power and do NOT interrupt power during the flash.
  3. Verify
    • Device Manager → expand Bluetooth / Network adapters / Keyboards → Properties → Driver tab → confirm the driver provider/version is Microsoft/Surface OEM. If anything shows a warning icon, note it.
F — Re‑enable updates and test safely
  1. Re‑enable updates with control
    • Option A (recommended for most): Settings → Windows Update → Advanced options → set “Notify me when a restart is required” and leave Wi‑Fi set to Metered to prevent auto download (Settings → Network & internet → Wi‑Fi → Properties → Set as metered). This gives you chance to approve the download.
    • Option B (manual): keep updates paused and manually download the KB from Microsoft Update Catalog when ready.
  2. Fresh image before the KB
    • Create one more image (quick incremental) with AOMEI so your rollback point is the very latest state.
  3. Install KB (if you choose)
    • Install the KB via Windows Update or the downloaded MSU. Reboot and test peripherals in this order: keyboard → Bluetooth pairing → Wi‑Fi connect. If any fail, stop and collect diagnostics.
G — Light storage I/O test (only if you want to check the community storage reports)
  1. Conservative approach
    • Copy 1–5 GB first, confirm OK. If stable, increase to 10–20 GB. Only attempt ~50 GB sustained writes if you accept the risk and have a verified image you can restore. Community reports tied heavy sustained writes (~50 GB) to issues after the August KB, so proceed with caution.
H — Recovery steps if anything goes wrong
  1. Restore from AOMEI
    • Boot the Surface from the AOMEI rescue USB → Restore → select the image → Restore system to original location → Start Restore. Follow prompts to finish and reboot. That returns you to the pre‑test system quickly.
  2. Driver troubleshooting (if only drivers err)
    • Device Manager → select problematic device → Roll Back Driver (if available) or Uninstall Device (do not delete driver files unless you have the OEM package), then reboot.
Diagnostics to capture (if you need my help to debug)
  • Screenshot of Device Manager with errors.
  • Event Viewer → Windows Logs → System (copy the Error entries timestamped when failure occurred).
  • Run (Admin PowerShell): Get-HotFix | Sort InstalledOn and pnputil /enum-drivers (I can give exact one‑liners if you want).
References / context I used
  • Backup strategy and imaging best practices.
  • Official Surface drivers/firmware guidance — use the Surface download page for your exact model.
  • KB rollout + storage caution: community reports link heavy sustained writes to risk after KB5063878; be conservative if you perform I/O stress tests.
Next: do you want me to
1) Give the exact AOMEI click‑by‑click commands and screenshots (I’ll walk you through each dialog), or
2) Give the exact PowerShell commands to capture driver lists and installed KBs so you can post them here after you image, or
3) Proceed later — you’ll follow this checklist and come back if anything trips?
Tell me which and I’ll produce the exact step-by-step screens / command lines.
 

Upvote 0 Downvote
ChatGPT said:
Good choice — AOMEI Backupper Standard is a solid, actively maintained free option for full‑disk images and rescue media. Below are clear, safe step‑by‑step instructions for: (A) preparing, (B) creating a verified image + rescue USB with AOMEI, and (C) the quick next steps (install Surface drivers, re‑enable updates, test). I’ll keep each step short and include exact menu names so you can follow on the Surface Laptop 2.
Why this order: make a verified image first, then update drivers, then enable/install the KB so you can roll back quickly if anything goes wrong. (Backing up first is the key best practice).
A — Preliminaries (do these before imaging)
  1. Hardware & power
    • Plug the Surface into AC power and connect the external USB drive (destination for the image). Use a USB drive at least as large as the used space on your system drive.
    • Have a spare USB stick (≥8 GB) for AOMEI rescue media.
  2. Suspend BitLocker (if enabled)
    • If BitLocker is on: Settings → Privacy & security → Device encryption / BitLocker → Suspend protection. This avoids decryption issues when restoring.
    • Re‑enable after testing/restoring.
  3. Close apps & disable sleep
    • Set Power & sleep settings to “Never” temporarily so the backup won’t be interrupted.
B — Install AOMEI Backupper Standard and create Rescue Media
  1. Download & install
    • Get AOMEI Backupper Standard from the official AOMEI site and install it.
  2. Create bootable rescue media (first thing after install)
    • Open AOMEI Backupper → Tools → Create Bootable Media.
    • Choose Windows PE (recommended) and build to your spare USB stick. Wait for completion. Keep this USB safe — you’ll use it to restore if needed.
  3. Test the rescue USB (optional but recommended)
    • Reboot the Surface, press and hold Volume Up + Power to boot to UEFI, choose Boot Options, and boot from the rescue USB to ensure it loads AOMEI’s recovery environment. Don’t proceed with restore — just verify it boots.
C — Create a verified full system image (System Backup)
  1. Start the backup
    • Open AOMEI Backupper → Backup → System Backup. AOMEI will auto‑select required system partitions (EFI, system, recovery).
    • Destination: choose the external USB drive.
  2. Advanced options (recommended)
    • Options → set compression level (Normal) and enable email notifications if you like.
    • Scheme → Enable if you want to keep only X latest backups (helps storage).
    • Before starting: click “Enable integrity check” or after the job completes use AOMEI’s Verify feature (see next step).
  3. Run & verify
    • Click Start Backup → wait until completed.
    • After completion, from the Backup Management view select the image → click “Explore Image” or “Check Image” to verify integrity. A verified image is essential.
D — Create a second image (optional, quick)
  • If you plan to install drivers immediately after this image, create a quick second image afterward so you have a snapshot right before you re‑enable updates. (That gives you a fresh rollback if drivers + KB cause problems.)
E — Install official Surface drivers & firmware (before re‑enabling KB)
  1. Get drivers
    • Go to Microsoft’s “Download drivers and firmware for Surface” page and choose Surface Laptop 2. Download the latest driver package/UEFI for your model.
  2. Install
    • Unzip the package, run the Surface_Drivers_xxx.msi (Run as Administrator). Follow prompts and reboot when asked.
    • If a firmware/UEFI package is included and prompts a firmware flash, do it only on AC power and do NOT interrupt power during the flash.
  3. Verify
    • Device Manager → expand Bluetooth / Network adapters / Keyboards → Properties → Driver tab → confirm the driver provider/version is Microsoft/Surface OEM. If anything shows a warning icon, note it.
F — Re‑enable updates and test safely
  1. Re‑enable updates with control
    • Option A (recommended for most): Settings → Windows Update → Advanced options → set “Notify me when a restart is required” and leave Wi‑Fi set to Metered to prevent auto download (Settings → Network & internet → Wi‑Fi → Properties → Set as metered). This gives you chance to approve the download.
    • Option B (manual): keep updates paused and manually download the KB from Microsoft Update Catalog when ready.
  2. Fresh image before the KB
    • Create one more image (quick incremental) with AOMEI so your rollback point is the very latest state.
  3. Install KB (if you choose)
    • Install the KB via Windows Update or the downloaded MSU. Reboot and test peripherals in this order: keyboard → Bluetooth pairing → Wi‑Fi connect. If any fail, stop and collect diagnostics.
G — Light storage I/O test (only if you want to check the community storage reports)
  1. Conservative approach
    • Copy 1–5 GB first, confirm OK. If stable, increase to 10–20 GB. Only attempt ~50 GB sustained writes if you accept the risk and have a verified image you can restore. Community reports tied heavy sustained writes (~50 GB) to issues after the August KB, so proceed with caution.
H — Recovery steps if anything goes wrong
  1. Restore from AOMEI
    • Boot the Surface from the AOMEI rescue USB → Restore → select the image → Restore system to original location → Start Restore. Follow prompts to finish and reboot. That returns you to the pre‑test system quickly.
  2. Driver troubleshooting (if only drivers err)
    • Device Manager → select problematic device → Roll Back Driver (if available) or Uninstall Device (do not delete driver files unless you have the OEM package), then reboot.
Diagnostics to capture (if you need my help to debug)
  • Screenshot of Device Manager with errors.
  • Event Viewer → Windows Logs → System (copy the Error entries timestamped when failure occurred).
  • Run (Admin PowerShell): Get-HotFix | Sort InstalledOn and pnputil /enum-drivers (I can give exact one‑liners if you want).
References / context I used
  • Backup strategy and imaging best practices.
  • Official Surface drivers/firmware guidance — use the Surface download page for your exact model.
  • KB rollout + storage caution: community reports link heavy sustained writes to risk after KB5063878; be conservative if you perform I/O stress tests.
Next: do you want me to
1) Give the exact AOMEI click‑by‑click commands and screenshots (I’ll walk you through each dialog), or
2) Give the exact PowerShell commands to capture driver lists and installed KBs so you can post them here after you image, or
3) Proceed later — you’ll follow this checklist and come back if anything trips?
Tell me which and I’ll produce the exact step-by-step screens / command lines.
Click to expand...
I have created the USB to boot from OK, but the backup is failing with this error

Information code 4122: Failed to get bitmap.​

 

Upvote 0 Downvote
Thanks — that AOMEI error (Information code 4122: Failed to get bitmap) is usually a backup/bitmap‑chain, VSS or destination accessibility problem rather than a random bug. Let’s troubleshoot in order from the fastest checks to the deeper fixes so you don’t lose time.
Quick summary of likely causes
  • Destination problems: not NTFS / insufficient space / flaky USB stick or hub.
  • VSS (Volume Shadow Copy) or snapshot failure so AOMEI can’t build the bitmap for the backup.
  • Corrupt or broken incremental/differential backup chain (AOMEI can’t read the previous bitmap).
  • Interference from BitLocker, AV/anti‑tamper or other backup software.
  • Underlying disk I/O errors (bad sectors) on source or destination.
    (These are the usual culprits reported in community testing and troubleshooting guides.)
Step‑by‑step checks & fixes (follow in this order)
1) Very quick checks (do these first)
  • Run AOMEI as Administrator (right‑click → Run as administrator).
  • Make sure destination is an external HDD/SSD (not a tiny USB thumb) formatted NTFS and has >= the used space of C:. AOMEI historically rejects small flash drives and prefers NTFS destinations.
  • Plug the drive directly into the Surface (no hub), try a different USB port/cable, and if possible use a powered USB port.
2) If you were doing incremental/differential backups: force a full backup
  • In AOMEI choose Backup → System Backup and pick “Full Backup” (or create a brand new backup job). If the backup chain is corrupted, starting a fresh full backup avoids the missing bitmap problem.
3) Suspend BitLocker & temporarily disable real‑time AV
  • If BitLocker is enabled: Settings → Privacy & security → Device encryption / BitLocker → Suspend protection.
  • Disable third‑party AV or any other backup/driver‑management tools while you run the image. These often block VSS. (Remember to re‑enable them afterward.)
4) Check VSS and snapshot state
Run these commands in an elevated (Admin) Command Prompt:
  • List writers (should report “No error” for each writer):
    vssadmin list writers
  • List current shadows:
    vssadmin list shadows
If the writers show errors or the list is empty, restart the service and try again:
net stop vss
net start vss
If you have old/corrupt shadows you’re comfortable deleting (this removes restore points), run:
vssadmin delete shadows /for=C: /all /quiet
Warning: deleting shadows removes restore points — only do it if you accept that.
VSS problems are a common root for “failed to get bitmap” because AOMEI needs a consistent shadow snapshot to build the bitmap.
5) Check disk health on both drives
  • Run CHKDSK on the system drive and on the external target (Admin CMD):
    chkdsk C: /f
    chkdsk E: /f (replace E: with your external drive letter)
  • Run basic system repairs:
    sfc /scannow
    DISM /Online /Cleanup-Image /RestoreHealth
Disk errors or filesystem corruption will break VSS / image creation and can cause that 4122 message.
6) Try a different destination (or network share)
  • If you can, point AOMEI at another external drive or to a network share (UNC \server\share) to rule out hardware failure on the target.
7) Recreate the rescue/boot media & retry (if imaging from WinPE)
  • You mentioned the rescue USB boots OK — good. If you used AOMEI’s built‑in PE builder and it misbehaves, recreate the PE rescue media and, if needed, write the ISO via Rufus instead — community reports show Rufus often fixes flaky PE USB boots. Test the backup from Windows (preferred) first, and only use WinPE rescue if necessary.
8) If it still fails: capture AOMEI logs and error text
  • AOMEI log location (common place): C:\ProgramData\AOMEI\Backupper\Logs\ — open the latest log file and copy the last 30–60 lines around the timestamp of the failed job. (You can also use AOMEI → Tools → Log Management to export logs.)
  • Post the exact error text + the final 20–40 lines of the AOMEI log here and I’ll read it — the logs usually show whether VSS, IO, or the bitmap chain failed and give the component name.
9) Workaround if you need immediate protection
  • If AOMEI keeps failing and you need a quick image now: use a different imaging tool (Rescuezilla or AOMEI Pro trial) to take a one‑off full image, or use Windows’ built‑in File History / OneDrive to protect your personal files while we sort the full image. Community guides recommend alternatives when AOMEI’s PE/backup path hits odd errors.
What I need from you if it still fails
  • Exact AOMEI error message (copy/paste) and time.
  • The last ~40 lines from the AOMEI log file (C:\ProgramData\AOMEI\Backupper\Logs).
  • Output (copy/paste) of:
    • vssadmin list writers
    • vssadmin list shadows
    • chkdsk results (if it ran and found/fixed anything)
If you prefer, I can give the exact commands and show how to find the log file step‑by‑step. Tell me which step you ran and what the output/log shows and I’ll point to the precise next action.
 

Upvote 0 Downvote
The Windows KB5063878 update is causing issues in some laptops by turning off the keyboard, Bluetooth, and Wi-Fi. The fix is to uninstall the update, but it can try to reinstall. To prevent that, suspend Windows Updates and use Microsoft's "Show or hide updates" tool to disable it. You can update Wi-Fi and Bluetooth drivers and make a restore point or backup before attempting the update again. Until Microsoft makes a fix, it is best to leave the update alone and uninstalled or blocked.
 

Upvote 0 Downvote
Yep — that’s the right diagnosis and the right practical plan. Uninstalling KB5063878 fixes the immediate device breakage, but Windows will try to reinstall it unless you block it; pausing updates and hiding that KB is the usual, safe workaround until Microsoft issues a corrected package.
Quick, safe checklist (do these in order)
  1. Create a fallback (do this first)
    • Make a full image or at minimum a System Restore point (use your backup tool or Macrium Reflect). This lets you recover quickly if anything else goes wrong while you test.
  2. Uninstall the broken update
    • Settings → Windows Update → Update history → Uninstall updates → find KB5063878 and uninstall.
    • (You can also check via elevated PowerShell: Get-HotFix -Id KB5063878, or use WMIC to list/uninstall: wmic qfe where HotFixID="KB5063878" list and wmic qfe where HotFixID="KB5063878" call uninstall).
  3. Prevent it from reinstalling (block the specific KB)
    • Pause Windows Updates: Settings → Windows Update → Pause updates for 7 days (repeat if necessary) to buy time.
    • Run Microsoft’s “Show or hide updates” troubleshooter (wushowhide.diagcab) and Hide KB5063878 so Windows Update won’t automatically reapply it. This is the reliable method used by most users.
  4. Update drivers / firmware (recommended before you ever re‑apply the KB)
    • Install the latest OEM drivers and firmware for Wi‑Fi and Bluetooth from the laptop maker (Surface/Dell/HP/Lenovo vendor pages). OEM driver updates often avoid the peripheral breakages that cumulative updates can trigger.
  5. If devices break again after any future install
    • Roll back drivers in Device Manager, or uninstall the device then reboot so Windows redetects and reinstalls the driver.
    • Run repairs from an elevated prompt: sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth.
  6. Control future driver/update behavior (optional)
    • If you prefer stricter control: set Wi‑Fi to Metered (reduces auto downloads) or enable the Group Policy “Do not include drivers with Windows Updates” to stop driver pushes via Windows Update.
A note about risk: KB5063878 was a cumulative security update — skipping it leaves your machine unpatched against the vulnerabilities it addresses. For many home users risk is lower than for servers or enterprise machines, but it isn’t zero. If you keep the KB hidden, consider hardening (firewall rules, avoid untrusted files/sites) until you can safely reapply the patch after verifying OEM drivers/firmware.
If you want, I can:
  • Walk you step‑by‑step through uninstalling the KB and running wushowhide.
  • Give exact commands for PowerShell/WMIC/wusa tailored to your Windows version.
  • Help download the correct OEM Wi‑Fi/Bluetooth drivers for your laptop model.
Which would you like me to do next?
 

Upvote 0 Downvote
You must log in or register to reply here.

Similar threads

J
  • Solved
Windows 7 Wi-Fi Stopped Working At Hotel After A Few Hours...Others Ok.
Replies
7
Views
2K
Mitchell_A
M
Back
Top