📎 AI Summary:
The thread centers on one Windows 11 machine not receiving or installing the optional August 2026 preview update KB5120998, while two others accepted it. Participants advised checking Update history, error codes, OS build, and whether the update was merely not offered; waiting is reasonable for an optional preview if regular security updates work, but not a guaranteed fix for installation failures. A separate complaint about Alt+F4 opening brightness controls was attributed tentatively to function-key or Fn-lock behavior rather than confirmed update changes, and the overall sentiment was frustrated but focused on gathering more details before troubleshooting.
D

daopa

Excellent Member
Member details
Joined
Jul 1, 2017
Messages
74
Thread Author #1
Chat, here I run 3 machines on W-11, one is reluctant to accept the last update :KB262009278. I have tried the provided check HD, and other in tools. Is there something else to do or jus be patient. Will it eventually accept this update ?
People are allowed on 2 machine but not this one. All other updates where accepted fine.
Light my candle. Jean
 

Last edited:
WindowsForum AI

WindowsForum AI

AI
Staff member
Robot
Member details
Joined
Mar 14, 2023
Messages
115,162
#2
daopa, one of your three Windows 11 machines is failing to accept the update, but we need the exact failure details. I couldn’t find an official Microsoft entry for KB262009278, so the number may contain a typo.
  1. Open Settings → Windows Update → Update history and share the update’s full name, KB number, and any error code.
  2. Press Win + R, type winver, and report the Windows version and OS build.
  3. Tell us whether the download stalls, installation fails, or Windows restarts and undoes the update.
  4. Your message ends at “provided check HD.” Which check did you run, and what result did it give?
A screenshot of the update error is fine too.
 
D

daopa

Excellent Member
Member details
Joined
Jul 1, 2017
Messages
74
Thread Author #3
WindowsForum AI said:
daopa, one of your three Windows 11 machines is failing to accept the update, but we need the exact failure details. I couldn’t find an official Microsoft entry for KB262009278, so the number may contain a typo.
  1. Open Settings → Windows Update → Update history and share the update’s full name, KB number, and any error code.
  2. Press Win + R, type winver, and report the Windows version and OS build.
  3. Tell us whether the download stalls, installation fails, or Windows restarts and undoes the update.
  4. Your message ends at “provided check HD.” Which check did you run, and what result did it give?
A screenshot of the update error is fine too.
Click to expand...
 
WindowsForum AI

WindowsForum AI

AI
Staff member
Robot
Member details
Joined
Mar 14, 2023
Messages
115,162
#4
Jean, your last reply contains only a quote of my previous message—no new details or screenshot came through.
  1. On the affected computer, open Settings → Windows Update and send a screenshot showing the update name and error, or type them here.
  2. Press Win + R, type winver, and tell us the version and OS build displayed.
We can’t yet tell whether waiting will help. Let’s identify the update and error before making any changes.
 
D

daopa

Excellent Member
Member details
Joined
Jul 1, 2017
Messages
74
Thread Author #5
Chat, I must be a master typoist, here is the data : 2026-08 Preview Update (KB5120998) (26200.9278). this from a good machine, I should look at the renegade before typing at you. Sorry, not too smart. Tomorrow. Jean
 
WindowsForum AI

WindowsForum AI

AI
Staff member
Robot
Member details
Joined
Mar 14, 2023
Messages
115,162
#6
No apology needed, Jean—those long update numbers are easy to mix up!
Since those details came from a working machine, let’s wait until you check the reluctant one tomorrow.
  1. Note its update name and KB number, plus any error code shown in Windows Update.
  2. Run winver and note its version and OS build.
  3. Tell us whether the update fails to download, fails to install, or simply isn’t offered.
That should help us work out whether waiting is appropriate or troubleshooting is needed. No need to change anything yet.
 

D

daopa

Excellent Member
Member details
Joined
Jul 1, 2017
Messages
74
Thread Author #7
Chat, hello.
Some more unneeded magic work from an update. I have used Alt F4 since DOS days to get to shutdown screen. No more, now it gives me screen brightness. Was this a positive improvement ? I beg no ! Who is the smart alec who did this ? Really no need to upset the apple cart.
 
WindowsForum AI

WindowsForum AI

AI
Staff member
Robot
Member details
Joined
Mar 14, 2023
Messages
115,162
#8
Hello Jean. I understand the annoyance when a familiar shortcut suddenly behaves differently.
Windows still supports Alt + F4 for the shutdown dialog when the desktop is active. We haven’t established that the update caused this.
The brightness response suggests your keyboard may be treating F4 as a brightness key rather than a function key—a possible Fn/F Lock issue, not yet a confirmed cause.
  1. Press Win + D to bring the desktop into focus, then try Alt + F4.
  2. If brightness appears again and your keyboard has an Fn key, try holding Fn + Alt + F4. This tests the keyboard’s alternate function-key behavior. If the shutdown dialog opens, press Esc to cancel.
  3. Tell me whether that works, and the computer or keyboard make and model, so we can check the correct function-lock setting for yours.
No need to undo an update or change drivers yet.
 
Last edited:
datawizard0103

datawizard0103

Excellent Member
Member details
Joined
Feb 14, 2024
Messages
245
#9
On the affected machine, first check Settings → Windows Update → Advanced options → Optional updates and make sure Preview updates are not being deferred. Also check Windows Update → Update history for a failed attempt and its error code. If there is no error and Windows simply has not offered it, I would leave it alone and wait for the next regular cumulative update. Since the other machines accepted it, this is more likely a rollout or machine specific compatibility issue than a bad hard drive.
 
WindowsForum AI

WindowsForum AI

AI
Staff member
Robot
Member details
Joined
Mar 14, 2023
Messages
115,162
#10
Thanks, datawizard0103—the distinction between “not offered” and “attempted but failed” is exactly what we need from Jean.
One small correction: Optional updates isn’t a preview-deferral control. The relevant user preference is “Get the latest updates as soon as they’re available” on the main Windows Update page; managed PCs may also have administrator policies. Jean needn’t enable it just for troubleshooting.
Skipping an optional non-security preview is reasonable if regular security updates install successfully; preview improvements normally flow into the following monthly security update. Waiting doesn’t guarantee that an installation failure will resolve, however.
Jean, when convenient:
  1. Open Settings → Windows Update → Update history on the affected machine and report any failed update’s exact name and error code.
  2. Tell us whether its most recent regular cumulative update installed successfully.
For now, neither a compatibility issue nor a disk fault has been established by the information posted.
 
Last edited:
harryjosh

harryjosh

Member
Member details
Joined
Sep 13, 2026
Messages
4
#11
Troubleshooting updates that fail or get stuck during Windows installation can be difficult because the cause can vary between systems. It would be helpful to include the Windows version, the exact installation or update error, and whether the process stops at a specific percentage or stage.
 

WindowsForum AI

WindowsForum AI

AI
Staff member
Robot
Member details
Joined
Mar 14, 2023
Messages
115,162
#12
Agreed, harryjosh. We still need details from Jean’s affected machine—the update information supplied earlier came from a working one.
Jean, please:
  1. Press Win + R, type winver, and report the Windows version and OS build.
  2. Check Settings → Windows Update → Update history for the failed update’s full name and error code.
  3. Tell us whether it isn’t offered, stalls downloading/installing (and at what percentage), or undoes changes after restarting.
No further system changes needed yet—those details will help us choose the next step rather than guess.
 
D

daopa

Excellent Member
Member details
Joined
Jul 1, 2017
Messages
74
Thread Author #13
WindowsForum AI said:
Hello Jean. I understand the annoyance when a familiar shortcut suddenly behaves differently.
Windows still supports Alt + F4 for the shutdown dialog when the desktop is active. We haven’t established that the update caused this.
The brightness response suggests your keyboard may be treating F4 as a brightness key rather than a function key—a possible Fn/F Lock issue, not yet a confirmed cause.
  1. Press Win + D to bring the desktop into focus, then try Alt + F4.
  2. If brightness appears again and your keyboard has an Fn key, try holding Fn + Alt + F4. This tests the keyboard’s alternate function-key behavior. If the shutdown dialog opens, press Esc to cancel.
  3. Tell me whether that works, and the computer or keyboard make and model, so we can check the correct function-lock setting for yours.
No need to undo an update or change drivers yet.
Click to expand...
 
WindowsForum AI

WindowsForum AI

AI
Staff member
Robot
Member details
Joined
Mar 14, 2023
Messages
115,162
#14
Jean, this post again contains only the quotation of my earlier reply—there is no result yet from the key test.
Please try the following on the affected PC:
  1. Press Win + D.
  2. Press Alt + F4.
  3. If brightness still changes, press Fn + Alt + F4.
  4. Reply with which combination opens the Shut Down Windows box, if either does.
  5. Include the computer make and model, if you can.
That will tell us whether the function-key mode changed, rather than Windows having removed the shutdown shortcut. The earlier thread details still show this as the likely next diagnostic step.
 
D

daopa

Excellent Member
Member details
Joined
Jul 1, 2017
Messages
74
Thread Author #15
Chat. Thanks, I went into the BIOS and changed that function key, ok now.
Why is MS playing with MY OWN BIOS ?

Sorry to say but I am now physically impaired, this might be my last post here. Thanks to all for the help. Jean
 
WindowsForum AI

WindowsForum AI

AI
Staff member
Robot
Member details
Joined
Mar 14, 2023
Messages
115,162
#16
Jean, I’m glad you found the setting and have Alt + F4 working again.
Windows itself normally does not reach into the BIOS and change one keyboard-function setting. What most likely happened is that the computer’s Fn/function-key mode changed in the firmware, perhaps after a BIOS/firmware update or a keyboard setting change. That is a hypothesis—we cannot confirm the cause without the PC model and update history.
Windows Update can deliver manufacturer-supplied UEFI/firmware updates on supported PCs, but the PC manufacturer’s firmware is responsible for applying them.
So: not necessarily Microsoft “playing” with your BIOS, but Windows Update may have carried a firmware package supplied for that machine.
And please don’t apologise, Jean. Thank you for letting us know the outcome. Take good care of yourself.
 

Last edited:
You must log in or register to reply here.