Win Update KB5083769 Windows 11 Cumulative Update build 26100.8246 (24H2) and 26200.8246 (25H2) - April 14


UPDATE 4/30:


 Microsoft Support:

April 14, 2026 - KB5083769 (OS Builds 26200.8246 and 26100.8246)​

This cumulative update for Windows 11, version 25H2 and 24H2 (KB5083769), includes the latest security fixes and improvements, along with non-security updates from last month’s optional preview release. To learn more about differences between security updates, optional non-security preview updates, out-of-band (OOB) updates, and continuous innovation, see Windows monthly updates explained. For information on Windows update terminology, see the different types of Windows software updates.

To view the latest updates about this release, visit the Windows release health dashboard or the update history page for Windows 11, version 25H2 and 24H2.


Announcements and messages

This section provides key notifications related to this release, including announcements, change logs, and end-of-support notices.

Windows Secure Boot certificate expiration​

Important: Secure Boot certificates used by most Windows devices are set to expire starting in June 2026. This might affect the ability of certain personal and business devices to boot securely if not updated in time. To avoid disruption, we recommend reviewing the guidance and taking action to update certificates in advance. For details and preparation steps, see Windows Secure Boot certificate expiration and CA updates.


Change log​


Improvements

This security update contains fixes and quality improvements from KB5079473 (released March 10, 2026), KB5085516 (released March 21, 2026), KB5079391 (released March 26, 2026 - no longer offered), and KB5086672 (released March 31, 2026). The following summary outlines key issues addressed by this update. Also, included are available new features. The bold text within the brackets indicates the item or area of the change.
  • [Secure Boot]
    • New! The status of Secure Boot certificate updates on your device may be displayed in the Windows Security app (Settings > Privacy & security > Windows Security). Learn more about the status alerts via badges and notifications. These enhancements are disabled by default on commercial devices.
    • With this update, Windows quality updates include additional high confidence device targeting data, increasing coverage of devices eligible to automatically receive new Secure Boot certificates. Devices receive the new certificates only after demonstrating sufficient successful update signals, maintaining a controlled and phased rollout.
    • This update addresses an issue where the device might enter BitLocker Recovery after the Secure Boot updates.
  • [Networking] This update improves reliability when Windows uses SMB compression over QUIC. After you install this update, SMB compression requests over QUIC complete more consistently, reducing the likelihood of timeouts and supporting smoother, more dependable performance.
  • [Remote Desktop] This update improves protection against phishing attacks that use Remote Desktop (.rdp) files. When you open an .rdp file, Remote Desktop shows all requested connection settings before it connects, with each setting turned off by default. A one-time security warning also appears the first time you open an .rdp file on a device. For more information, see Understanding security warnings when opening Remote Desktop (RDP) files.
  • [Reset this PC (known issue)] Fixed: This update addresses an issue that might cause device reset to fail when using the “Keep my files” or “Remove everything” options. This might occur after installing the March 2026 (KB5079420) Hotpatch security update.
  • [Vulnerable driver blocklist] This update introduces a security hardening change that adds known vulnerable kernel drivers to the Microsoft vulnerable driver blocklist. Backup applications that rely on blocked drivers might experience failures when attempting to mount or manage disk images.

    These apps relying on blocked drivers might display error messages, including "The backup has failed because Microsoft VSS has timed out during the snapshot creation" or VSS_E_BAD_STATE. Affected users should update to a newer version of their application that uses newer drivers that include the required protections. For more information, see April 2026 Windows security updates introduce protections to known vulnerable kernel drivers.
If you've already installed previous updates, your device will download and install only the new updates included in this package.

For more information about security vulnerabilities, see the Security Update Guide and the April 2026 Security Updates.

AI Components

This release updates the following AI components:

AI Component​
Version​
Image Search1.2603.377.0
Content Extraction1.2603.377.0
Semantic Analysis1.2603.377.0
Settings Model1.2603.377.0

Windows 11 servicing stack update (KB5088467)- 26100.8247

This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates. To learn more about SSUs, see Simplifying on-premises deployment of servicing stack updates.


Known issues in this update

Symptom

Some devices with an unrecommended BitLocker Group Policy configuration might be required to enter their BitLocker recovery key on the first restart after installing this update.

This issue only affects a limited number of systems in which ALL of the following conditions are true. These conditions are unlikely to be found on personal devices not managed by IT departments.
  1. BitLocker is enabled on the OS drive.
  2. The Group Policy "Configure TPM platform validation profile for native UEFI firmware configurations" is configured, and PCR7 is included in the validation profile (or the equivalent registry key is set manually).
  3. System Information (msinfo32.exe) reports Secure Boot State PCR7 Binding as "Not Possible".
  4. The Windows UEFI CA 2023 certificate is present in the device’s Secure Boot Signature Database (DB), making the device eligible for the 2023‑signed Windows Boot Manager to be made the default.
  5. The device is not already running the 2023-signed Windows Boot Manager.
In this scenario, the BitLocker recovery key only needs to be entered once -- subsequent restarts will not trigger a BitLocker recovery screen, as long as the group policy configuration remains unchanged. For help finding your BitLocker recovery key, see the article, Find your BitLocker recovery key.

Enterprises are recommended to audit their BitLocker group policies for explicit PCR7 inclusion and check msinfo32.exe for their PCR7 binding status before installing this update. (See Option 1 below.)

Workaround

This issue is addressed in KB5089549. After installing KB5089549, devices with this incompatible group policy configuration are prevented from installing the 2023-signed Windows Boot Manager. If your device was impacted, Event ID 1032 will appear in the System event log when installing Windows updates: "The Secure Boot update Boot Manager (2023) was not applied due to a known incompatibility with the current BitLocker configuration."

If you receive Event ID 1032, Microsoft strongly recommends removing the Group Policy configuration before installing updates so that you can install the 2023-signed Windows Boot Manager and continue to receive the latest Secure Boot protections.

Remove the Group Policy configuration before installing the update (Recommended)
  1. Open Group Policy Editor (gpedit.msc) or your Group Policy Management Console.
  2. Navigate to: Computer Configuration > Administrative Templates > Windows Components > BitLocker Drive Encryption > Operating System Drives.
  3. Set "Configure TPM platform validation profile for native UEFI firmware configurations" to "Not Configured".
  4. Run the following command on affected devices to propagate the policy change: gpupdate /force
  5. Run the following command to suspend BitLocker (where BitLocker is enabled on the C: drive): manage-bde -protectors -disable C:
  6. Run the following command to resume BitLocker (where BitLocker is enabled on the C: drive): manage-bde -protectors -enable C:
  7. This updates the BitLocker bindings to use the Windows-selected default PCR profile.
If you do not wish to remove this Group Policy configuration, you can install the new Windows Boot Manager by temporarily suspending BitLocker and installing the Secure Boot update. To do this:
  1. Run the following command to suspend BitLocker (if BitLocker is enabled on the C: drive): manage-bde -protectors -disable C:
  2. Run the following command: Start-ScheduledTask -TaskName "\Microsoft\Windows\PI\Secure-Boot-Update"
  3. Restart the device.
  4. Once the new Windows Boot Manager is successfully installed, enable BitLocker by running the command: manage-bde -protectors -enable C:

Symptoms

After installing this update, the security warning that appears when opening Remote Desktop (RDP) files might not display correctly in some cases.

This issue can occur when you use more than one monitor with different display scaling settings (for example, one display set to 100% and another set to 125%). When this happens, the warning window might show overlapping text or partially hidden buttons, which can make the message difficult to read or interact with.

Workaround

This issue is addressed in KB5083631.

How to get this update

Before you install this update

Microsoft combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). For general information about SSUs, see Servicing stack updates.

Install this update

To install this update, use one of the following Windows and Microsoft release channels.

Available​
Next Step​
Included
This update downloads and installs automatically from Windows Update and Microsoft Update.
Included
To install this release from the Microsoft Update Catalog, select the option that matches your device architecture (arm64 or x64), and then follow the instructions.

If you want to remove this update

Caution: Before you decide to remove this update, see Understanding the risks: Why you should not uninstall security updates.
To remove the LCU after installing the combined SSU and LCU package, use the DISM/Remove-Package command line option with the LCU package name as the argument. You can find the package name by using this command: DISM /online /get-packages.

Running Windows Update Standalone Installer (wusa.exe) with the /uninstall switch on the combined package will not work because the combined package contains the SSU. You cannot remove the SSU from the system after installation.

File information

For a list of the files provided in this update, download the file information for cumulative update 5083769.

For a list of the files provided in the servicing stack update, download the file information for the SSU (KB5088467) - version 26100.8247.



 Source:



Check Windows Updates


ISO from Microsoft Media Creation Tool (MCT):


UUP Dump:

64-bit ISO download:

ARM64 ISO download:

 
Last edited:

My Computers

System One System Two

  • OS
    Windows 11 Pro 24H2
    Computer type
    PC/Desktop
    Manufacturer/Model
    Multi
    CPU
    Intel i9-9900k
    Motherboard
    Gigabyte Z390 Aorus Master
    Memory
    Corsair Vengeance LPX 32GB (2 x 16GB)
    Graphics Card(s)
    Gigabyte RTX 2080Ti Gaming OC
    Monitor(s) Displays
    Samsung LC32HGQ
    Screen Resolution
    WQHD
    Hard Drives
    Samsung 970 Evo Plus 1 TB
    Crucial MX100 512 GB
    Samsung 840 Pro 256 GB
    Seagate ST4000DM000-1F2168 4 TB
    PSU
    Seasonic P-860 Platinium
    Case
    Corsair Graphite 780T
    Cooling
    Noctua NH-U14S
    Keyboard
    Corsair K70 MK.2 Low profile
    Mouse
    Logitech G Pro HERO
    Internet Speed
    200 Mb/s
    Browser
    Mozilla Firefox
    Antivirus
    Windows Defender
    Other Info
    BIOS version F11
  • Operating System
    Windows 11 Home 24H2
    Computer type
    Laptop
    Manufacturer/Model
    Clevo W650KJ1
    CPU
    Intel i5 7500
    Motherboard
    Clevo W65KK/KJ1
    Memory
    2×8 Go Corsair Vengeance 2400Mhz DDR4
    Graphics card(s)
    Nvidia GeForce GTX 1050
    Sound Card
    Integrated
    Screen Resolution
    1920x1080
    Hard Drives
    Samsung 850 Evo M.2 SATA 250 GB
    Seagate ST1000LM035 1 TB
    Browser
    Mozilla Firefox
    Antivirus
    Windows Defender
    Other Info
    Replaced original Wi-Fi card by an Intel® Wireless-AC 9260
    BIOS version 1.05.13

My Computer

System One

  • OS
    Windows 11, version 25H2 (26200)
    Computer type
    PC/Desktop
    CPU
    AMD Ryzen 9 9950X 16-Core Processor
    Motherboard
    ASRock B650M PG Riptide
    Memory
    DDR5-6000 (CL36) 64.0 GB
    Graphics Card(s)
    NVIDIA GeForce RTX 4090
    PSU
    1200W
    Case
    Phanteks Enthoo Pro 2
    Cooling
    Noctua NH-D12L
This is not necessary. When you are on 26200.8246 and secure boot inside your BIOS is turned on; the option will appear under Device security inside Defender. If it's reflecting the BIOS status or does some more checks is unknown.

One note on that ViVetool; those numbers are feature dependent and are active for a certain period. Once the feature has been implemented those
Thank you very much. At first, I thought it was just a ViveTool issue, but by following the thread little by little, I managed to figure out and solve all the steps, including resetting the BIOS because it wasn't showing the options to activate Secure Boot Control.
 

Attachments

  • 002.webp
    002.webp
    67 KB · Views: 2
Last edited:

My Computer

System One

  • OS
    Windows 11 25H2 of UPP
    Computer type
    PC/Desktop
    Manufacturer/Model
    Wallapop
    CPU
    Intel Core i5-7600 3.5GHz
    Motherboard
    MSI Z270 GAMING M3
    Memory
    64 Gb Crucial Ballistix 3200MHz
    Graphics Card(s)
    MSI GeForce GTX 1050 Ti
    Monitor(s) Displays
    GL2450HT 24"
    Screen Resolution
    1920 x 1080 pixels
    Hard Drives
    Kingston A250 SSD
Running fine on my PC.
 

My Computer

System One

  • OS
    Windows 11 Pro 25H2
    Computer type
    Laptop
    Manufacturer/Model
    Acer Predator Helios 300 PH314-54-72ZJ
    CPU
    Intel Core i7-11800H
    Motherboard
    TGL
    Memory
    16GB (2x8 GB)
    Graphics Card(s)
    RTX 3060 Laptop GPU
    Sound Card
    Realtek ALC295
    Monitor(s) Displays
    1
    Screen Resolution
    2560 x 1440 @ 165Hz
    Hard Drives
    1TB NVMe SSD, 512GB NVMe SSD, 1TB 7200 RPM HDD
    Cooling
    Aeroblade 5th Gen 3D fan
    Keyboard
    RGB Laptop keyboard
    Mouse
    Logitech Lightsync G203
    Internet Speed
    175 Mbps up/175 Mbps down
    Browser
    Firefox with uBlock Origin and YouTube enhancing extensions..
    Antivirus
    Windows Security with Core Isolation on
I have an old computer from 2017 with an Intel 1151 processor. I can't understand how Windows 25h2 and most of its updates are barely causing me any problems, and certainly not the level of issues they're causing for other users. I just hope they can fix the incompatibilities for newer computers, because I gave up on researching and trying to find a replacement for my old machine a long time ago.

One of the things that surprised me most after installing 25h2 was that it installed the same drivers as with 22h2, and the manual drivers I installed without any problems were all for 22h2.
 

My Computer

System One

  • OS
    Windows 11 25H2 of UPP
    Computer type
    PC/Desktop
    Manufacturer/Model
    Wallapop
    CPU
    Intel Core i5-7600 3.5GHz
    Motherboard
    MSI Z270 GAMING M3
    Memory
    64 Gb Crucial Ballistix 3200MHz
    Graphics Card(s)
    MSI GeForce GTX 1050 Ti
    Monitor(s) Displays
    GL2450HT 24"
    Screen Resolution
    1920 x 1080 pixels
    Hard Drives
    Kingston A250 SSD
KB5077181 back in February introduced an annoying issue for me. Every time I'd cold boot after updating, I'd get a Please Wait screen for a few seconds before I was able to log in. Ultimately harmless since it was for just a few seconds and didn't affect being able to log in, but drove me up the wall because even with the goofiness of 24H2 I knew it wasn't s'posed to be doing that. After over a month of trying to wait it out and throwing every solution I could find at it to no avail (and seeing if last month's update would fix it, which it did not), I finally did a repair install and the issue was gone.

It came back with this update. After several days, it came down to either uninstalling the update (I didn't have that option back in February) or doing another repair install, and I didn't want to do the latter again so soon after the last one. Uninstalled it yesterday and put updates on pause for the time being.

Today, there is peace. No Please Wait screen greeted me on boot, solidifying that the issue was never on my end. Fix your stuff, Microsoft.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    ibuypower
    CPU
    Intel i3-12100F
    Motherboard
    AsRock B660M-C
    Graphics Card(s)
    NVIDIA GeForce GTX 1650
24H2 ruined networking for me. All my PC's are still using 23H2. I have 24H2 on one box that I use to see if any of the updates fix the issue. I have tried all the suggestions made from several other threads discussing network problems 24H2 caused but NONE of them fixed:

Missing NAS devices
Missing PCs
The PC I'm on doesn't show in Network until I add it to Quick Access by using its \\MissingPCName.

So yeah, I'm hard headed. Sorry Microsoft I just want my network to work like it always had!
 

My Computer

System One

  • OS
    Windows 11 Pro 23H2
    Computer type
    PC/Desktop
    Manufacturer/Model
    MinisForum
    CPU
    Intel(R) Core(TM) i9-12900HK
    Memory
    32gb
    Graphics Card(s)
    Intel(R) Iris(R) Xe Graphics
    Sound Card
    Realtek 888
    Monitor(s) Displays
    Acer
    Screen Resolution
    1920x1080
    Hard Drives
    1TB SSD
    Keyboard
    Logitech
    Mouse
    Logitech MX Master 2X
    Internet Speed
    1GB
    Browser
    Firefox
    Antivirus
    Windows Defender
24H2 ruined networking for me. All my PC's are still using 23H2. I have 24H2 on one box that I use to see if any of the updates fix the issue. I have tried all the suggestions made from several other threads discussing network problems 24H2 caused but NONE of them fixed:

Missing NAS devices
Missing PCs
The PC I'm on doesn't show in Network until I add it to Quick Access by using its \\MissingPCName.

So yeah, I'm hard headed. Sorry Microsoft I just want my network to work like it always had!
I was having issues seeing my network drives on my new PC last week. I had success with some of the answers on this thread:

New computer can't see my shared drives
 

My Computers

System One System Two

  • OS
    Win 11 Pro (25H2 RP)
    Computer type
    Laptop
    Manufacturer/Model
    Acer AN515-54
    CPU
    Intel(R) Core(TM) i5-9300H CPU @ 2.40GHz 2.40 GHz
    Memory
    32GB
    Graphics Card(s)
    Nvidia GeForce GTX 1650, Intel UHD 630
    Monitor(s) Displays
    Acer CB272D
    Screen Resolution
    1920x1080
    Hard Drives
    256GB and 1T SSD
    Internet Speed
    500MB
    Browser
    Edge (Stable)
    Antivirus
    Microsoft Defender
  • Operating System
    Win 11 Pro (RP)
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo Legion 5 16IAX10 - Type 83NX
    CPU
    Intel(R) Core(TM) Ultra 9 275HX (2.70 GHz)
    Memory
    32GB DDR5-5600
    Graphics card(s)
    NVIDIA® GeForce RTX™ 5060 8GB
    Monitor(s) Displays
    Acer CB272D
    Screen Resolution
    1920x1080 75Hz
    Hard Drives
    WD Green SN3000 (2TB)
    Samsung Portable T5 (2TB)
    Keyboard
    Logi MX Keys
    Mouse
    Logi MX Anywhere 3
    Internet Speed
    500MB
    Browser
    Edge
    Antivirus
    MS Defender
24H2 ruined networking for me. All my PC's are still using 23H2. I have 24H2 on one box that I use to see if any of the updates fix the issue. I have tried all the suggestions made from several other threads discussing network problems 24H2 caused but NONE of them fixed:

Missing NAS devices
Missing PCs
The PC I'm on doesn't show in Network until I add it to Quick Access by using its \\MissingPCName.

So yeah, I'm hard headed. Sorry Microsoft I just want my network to work like it always had!
Based on what you said here, this is correct behavior in Windows 11 23H2 vs 25H2. There have been background security changes including encryption changes that causes this to occur. Microsoft has an article detailing these changes and I cannot find it right now. The Windows 11 discovery services (
Function Discovery Provider Host, Function Discovery Resource Publication, SSDP Discovery, UPnP Device Host) with the correct network configuration and sharing settings are needed. I see the same sharing behavior in Linux with SMB until properly configured discovery services (such as avahi-daemon and wsdd, and others). I have dealt with these network changes over the years and understand why some comptuers/devices do not show on the network.

Basically your Windows 11 23H2 system are more open and prone to attack than someone using 25H2.

If you can access the computer/device over the network using \\192.168.x.x or \\hostname, sharing is working properly. Discovery services not finding network devices is a different issue.
 

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell 16 Plus DB16255
    CPU
    AMD Ryzen AI 7 350 w/ Radeon 860M 50 TOPS
    Motherboard
    Dell 0PKMHG
    Memory
    32GB LPDDR5X 7500 MT/s
    Graphics Card(s)
    AMD Radeon 860M integrated (shared memory)
    Sound Card
    Stereo speakers (2.5 W x 2 = 5 W total peak)/Realtek SounzReal/Dolby Atmos
    Monitor(s) Displays
    Displays: 16" 1920 x 1200 (Full HD+/WUXGA) 300 nits 60Hz *** Samsung - 27” Odyssey FHD IPS 240Hz G-Sync Gaming Monitor
    Screen Resolution
    1920x1080 @ 60Hz
    Hard Drives
    EG6 KIOXIA 1TB NVME
    Case
    Ice Blue
    Cooling
    "dual-fan" or "enhanced" air-cooling system
    Mouse
    Logitech M650 Wireless/Bluetooth
    Internet Speed
    800/600 Fiber

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell 16 Plus DB16255
    CPU
    AMD Ryzen AI 7 350 w/ Radeon 860M 50 TOPS
    Motherboard
    Dell 0PKMHG
    Memory
    32GB LPDDR5X 7500 MT/s
    Graphics Card(s)
    AMD Radeon 860M integrated (shared memory)
    Sound Card
    Stereo speakers (2.5 W x 2 = 5 W total peak)/Realtek SounzReal/Dolby Atmos
    Monitor(s) Displays
    Displays: 16" 1920 x 1200 (Full HD+/WUXGA) 300 nits 60Hz *** Samsung - 27” Odyssey FHD IPS 240Hz G-Sync Gaming Monitor
    Screen Resolution
    1920x1080 @ 60Hz
    Hard Drives
    EG6 KIOXIA 1TB NVME
    Case
    Ice Blue
    Cooling
    "dual-fan" or "enhanced" air-cooling system
    Mouse
    Logitech M650 Wireless/Bluetooth
    Internet Speed
    800/600 Fiber

My Computers

System One System Two

  • OS
    Windows 11 Pro for Workstations
    Computer type
    PC/Desktop
    Manufacturer/Model
    Custom self build
    CPU
    Intel i7-8700K 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING (11GB GDDR5X)
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G75 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO M.2,
    TerraMaster F8 SSD Plus NAS
    PSU
    Seasonic Prime Titanium 850W
    Case
    Thermaltake Core P3 wall mounted
    Cooling
    Corsair Hydro H115i
    Keyboard
    Amazon Basics Wired Full Keyboard MD005
    Mouse
    Logitech MX Master 4
    Internet Speed
    2 Gbps Download and 100 Mbps Upload
    Browser
    Chrome and Edge
    Antivirus
    Microsoft Defender
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    CyberPower CP1500PFCLCD
    Galaxy S23 Plus phone
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Surface Laptop 7 Copilot+ PC
    CPU
    Snapdragon X Elite (12 core) 3.42 GHz
    Memory
    16 GB LPDDR5x-7467 MHz
    Monitor(s) Displays
    15" HDR
    Screen Resolution
    2496 x 1664
    Hard Drives
    1 TB SSD
    Internet Speed
    Wi-Fi 7 and Bluetooth 5.4
    Browser
    Chrome and Edge
    Antivirus
    Microsoft Defender
I also have a keyboard issue following this update. Function F2 on my keyboard should reduce brightness, and Function F3 should increase it. Neither work now. I can still change screen brightness using the settings option.
Other function keys, such as sound volume and Prt Sc work as expected.
My keyboard issues have returned in the same keys of mine w/ the 2WS and volume keys and I been battling it for the past 30 minutes, ughh I hope this isn't an hardware issue this laptop is only 1 year old.
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    Laptop
    Manufacturer/Model
    HP
    Memory
    15GB RAM
    Hard Drives
    SSD 1TB
    Browser
    Chrome
In the current Secure Boot guidelines, you're supposed to check if BitLocker is enabled or not before updating certs.

Whenever it's enabled, temporarily disable or suspend BitLocker before applying certs because TPM will detect something's changed and ask for a recovery password. It sounds like some IT admins aren't paying attention to the guidelines.
 

My Computer

System One

  • OS
    Windows 7
My keyboard issues have returned in the same keys of mine w/ the 2WS and volume keys and I been battling it for the past 30 minutes, ughh I hope this isn't an hardware issue this laptop is only 1 year old.
Came to an interesting realization: could this be overheating instead rather than the update? temps here have jumped to the 70's-80's alot and when this first began, it was incredibly humid in the late 80's of temps

My room is prone to building heat and I don't have my AC yet, my laptop's battery sits right under the 2 W S keys with some heat reaching the volume keys I mentioned before

Could it be a temp-related overheating? any keyboard experts here can help?
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    Laptop
    Manufacturer/Model
    HP
    Memory
    15GB RAM
    Hard Drives
    SSD 1TB
    Browser
    Chrome
 

My Computer

System One

  • OS
    Win 11 Pro 25H2 ARM64 (Parallels VM) _ 26200.8457
    Computer type
    Laptop
    Manufacturer/Model
    MacBook Pro (13-inch, M1, 2020)
    CPU
    Apple Silicon M1 / 3.20 GHz (4 processors)
    Memory
    16 GB
    Monitor(s) Displays
    13.3-inch (2560 × 1600)
    Antivirus
    N360 for Mac / Win / Win Defender
    Other Info
    Parallels Pro 26.3.3/ macOS Tahoe 26.5
 

My Computer

System One

  • OS
    Win 11 Pro 25H2 ARM64 (Parallels VM) _ 26200.8457
    Computer type
    Laptop
    Manufacturer/Model
    MacBook Pro (13-inch, M1, 2020)
    CPU
    Apple Silicon M1 / 3.20 GHz (4 processors)
    Memory
    16 GB
    Monitor(s) Displays
    13.3-inch (2560 × 1600)
    Antivirus
    N360 for Mac / Win / Win Defender
    Other Info
    Parallels Pro 26.3.3/ macOS Tahoe 26.5

My Computers

System One System Two

  • OS
    Windows 11 Pro for Workstations
    Computer type
    PC/Desktop
    Manufacturer/Model
    Custom self build
    CPU
    Intel i7-8700K 5 GHz
    Motherboard
    ASUS ROG Maximus XI Formula Z390
    Memory
    64 GB (4x16GB) G.SKILL TridentZ RGB DDR4 3600 MHz (F4-3600C18D-32GTZR)
    Graphics Card(s)
    ASUS ROG-STRIX-GTX1080TI-O11G-GAMING (11GB GDDR5X)
    Sound Card
    Integrated Digital Audio (S/PDIF)
    Monitor(s) Displays
    2 x Samsung Odyssey G75 27"
    Screen Resolution
    2560x1440
    Hard Drives
    1TB Samsung 990 PRO M.2,
    4TB Samsung 990 PRO M.2,
    TerraMaster F8 SSD Plus NAS
    PSU
    Seasonic Prime Titanium 850W
    Case
    Thermaltake Core P3 wall mounted
    Cooling
    Corsair Hydro H115i
    Keyboard
    Amazon Basics Wired Full Keyboard MD005
    Mouse
    Logitech MX Master 4
    Internet Speed
    2 Gbps Download and 100 Mbps Upload
    Browser
    Chrome and Edge
    Antivirus
    Microsoft Defender
    Other Info
    Logitech Z625 speaker system,
    Logitech BRIO 4K Pro webcam,
    HP Color LaserJet Pro MFP M477fdn,
    CyberPower CP1500PFCLCD
    Galaxy S23 Plus phone
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Surface Laptop 7 Copilot+ PC
    CPU
    Snapdragon X Elite (12 core) 3.42 GHz
    Memory
    16 GB LPDDR5x-7467 MHz
    Monitor(s) Displays
    15" HDR
    Screen Resolution
    2496 x 1664
    Hard Drives
    1 TB SSD
    Internet Speed
    Wi-Fi 7 and Bluetooth 5.4
    Browser
    Chrome and Edge
    Antivirus
    Microsoft Defender
You know they recently added the Device Encryption switch under privacy & security to two of my machines on this and an RP update. I didn't think I would have encryption keys though since I left them disabled. Will I was wrong, I went to my MS account and both machines now have Bit locker keys assigned. Decided I better make copies of them just incase MS did something crazy on an update like enable them without my say or knowledge. Not like I'm being paranoid but OK I am being paranoid. Murphy's law and all that you know.
 

My Computers

System One System Two

  • OS
    Windows 11 25H2
    Computer type
    Laptop
    Manufacturer/Model
    Alienware 18 Area-51
    CPU
    Intel Core Ultra 9 275HX (24-Core)
    Motherboard
    Alienware
    Memory
    64GB DDR5 6400MT/s
    Graphics Card(s)
    NVIDIA GeForce RTX 5080 and Intel UHD Graphics
    Sound Card
    Onboard, Realtek high-performance Audio chips (ALC3329 & ALC1708))
    Monitor(s) Displays
    300HZ 18-inch QHD 500 nit Comfort View+
    Screen Resolution
    2560 x 1600
    Hard Drives
    2TB NVMe M.2 PCIe Gen 5 SSD
    Case
    Magnesium Alloy
    Cooling
    Advanced Cryo-Tech Quad-Fan Cooling system & large vapor chamber
    Keyboard
    Cherry MX ultra low profile mechanical keyboard with per key AlienFX RGB lighting
    Mouse
    Logitech MX Master 4
    Browser
    Vivaldi (main), Firefox, Chrome, Edge
    Antivirus
    MS Defender and Malwarebytes Free
  • Operating System
    Windows 11 25H2
    Computer type
    Laptop
    Manufacturer/Model
    Microsoft Surface Laptop 7
    CPU
    Qualcomm Snapdragon X Elite (12 Core) ARM based CPU
    Motherboard
    Microsoft Corp.
    Memory
    16GB LPDDR5
    Graphics card(s)
    Qualcomm Adreno X1-85
    Sound Card
    Omnisonic speakers with Dolby Atmos spatial sound
    Monitor(s) Displays
    120 Hz 13.8-inch 600 nit PixelSense Flow touchscreen
    Screen Resolution
    2304x1536
    Hard Drives
    1TB NVMe Gen 4 SSD
    Case
    Anodized Aluminum
    Cooling
    Traditional active cooling fan system
    Keyboard
    Mechanical QWERTY, backlit when in use
    Mouse
    Logitech MX Master 4 and Surface Arc Mouse
    Browser
    Vivaldi (main), Firefox, Chrome, Edge
    Antivirus
    MS Defender and Malwarebytes Free
WOW, I just found out a little while ago that I had Device encryption On. Probably was enabled by this update or by a repair install I did a month ago. Anyway, thanks to the videos posted by @DSAND1 I realized that Device encryption was On. My drive was not fully encrypted since I do not use a Microsoft account but this scared the hell out of me. I am on W11 Home. I am still shaking but I disabled Device encryption after watching the videos and ran this command to make sure it was Off and all well afterward> manage-bde -status

DE.webp

Bo
 

My Computer

System One

  • OS
    Windows11
    Computer type
    PC/Desktop
    Manufacturer/Model
    HP
    Memory
    16GB
    Keyboard
    HP 310
    Mouse
    HP
    Browser
    Firefox
KB5083769 issues with start

Start closes after a split second.

The problem is cured by uninstalling the Update. I reproduced this phenomenon on 3 installations including the clean installation.

The final answer came to me after I created a USB drive with Rufus without update. The start was fine immediately after the installation and the problem came after the Update.
 

My Computer

System One

  • OS
    windows 11 ,Ubuntu Cinnamon - for tinkering only
    Computer type
    PC/Desktop
    Manufacturer/Model
    No Name - Assembled by a Compute shop in a Strip Mall.
    CPU
    Intel i511400
    Motherboard
    ASUS PRIME B560-PLUS motherboard
    Memory
    16 GB
    Graphics Card(s)
    0
    Sound Card
    0
    Monitor(s) Displays
    25 in BenQ
    Screen Resolution
    1920 x 1080
    Hard Drives
    9 SSDs 4 Nvme, 2 in M.2 slot and 2 in PCIE with adapter + 5 Sata. DVD drive
    PSU
    600w
    Case
    Antec- VSK4000E-U3 Mid Tower
    Internet Speed
    Bell pure fibre optic. 1 GB package. Wireless adapter +/- 500/500
    Browser
    Firefox, Microsoft Edge
    Antivirus
    Defender
Back
Top Bottom