Help, using Mac Bluetooth Keyboard on PC?


Recommended Posts

Maybe you should try to switch stack from Microsoft to Widcomm, or vice versa?

585919603[/snapback]

I started with old Widcomm's, was it 1.3xx as it worked with it as I described. I also tried with Xp SP2's stack and it worked the same.

I've tried with widcomm 1.4xx and 3xx and with both the keyb didn't work. The PIN-code sections was grayed out as many ahs described. Haven't tried the version 4 yet, because all those widcomm versions I have tried are provided by Logitech and I haven't gotten any of the cracked versions work. But I'll try the version 4...

Hope it helps.

please help!! i have been trying this for ages and am just about to return the keyboard. i have d-link 120 bluetooth in my pc but it uses the xp sp2 drivers as they knock out the d-link software. is this possible to link with the d-link dongle and the microsoft drivers if so please could someone post a step by step. would be much appreciated as i am at my wits end trying this. the bluetooth finds the keyboard recognises it but thats about it. i tried without a passkey. keyboard didn't work and the pairing ended. help!! :( :no:

hi

i had the same problem with the belkin bluetooth adapter, so i uninstalled the belkin software and let widows xp sp2 find the bluetooth dongle.then i asked it add devices, it found the keyboard so i tried not assignig a passkey but windows told me everything was fine but the keyboard didn't work. so i asked windows to give the keyboard a passkey, i then pressed enter and added the key, works fine now. and looks lovely set up as part of my media centre.

585844389[/snapback]

tried this without passkey. so adding a pass key made it work yeah??

could it be that simple

  • 4 weeks later...

Using a Micro$oft Bluetooth 2.0 adapter and an Apple wireless keyboard was effortless to get to work together. It seems that people must be having problems with M$ Bluetooth 1.? adapters or some other Bluetooth Adapter.

The only problem is that the "=" on the number pad does not work BUT this can be remapped by using Sharpkeys. There is no scroll lock, print screen or pause break key either and all but the pause/break key can be remapped (who needs a scroll lock key anyways?)

Unfortunately, the volume up/down, mute and eject buttons don't work and I cannot find a work around for these.

The "clear" button maps automatically as a number lock key (this can also be remapped by Sharpkeys as well)

Where did i get a 2.0 adapter? ... Ebay of course (the only one I've seen - must of been with a keyboard or mouse combo unit from M$ that the seller didn't want or need).

The personal area network with Bluetooth Network Connection also automatically configured. (M$ must of worked the bugs out ... now they just need to sell the bluetooth usb item by itself).

  • 1 month later...

Boy was this a pain in the neck to figure out... and the solution isn't 100% pretty,

but it sure works well! I've come to the conclusion that the MX900's BT hub is not

that great... and D-Link's DBT-120 USB hub is wonderful! The 3.x WIDCOMM drivers

just don't like the Apple Wireless Keyboard in that it won't pair correctly since

the pairing key is never displayed (as mentioned by previous poster). Funny enough

the 1.x WIDCOMM drivers do infact work.... BUT the Apple Wireless keyboard

fails to connect at login time leaving you without a way to enter a password in

during login if you use the MX900 + WIDCOMM solution. SO in the end here is what

I used :

NO WIDCOMM drivers. I installed Logitech's Setpoint 2.2, but then unistalled WIDCOMM.

Use the DBT-120. That little sucker rocks!

Use Microsoft's Bluetooth stack... ugly windows but works great!

Only plug the MX900 base into the AC adapter and not into the computer...

(this disables the MX900's BT hub, but allows it to recharge the mouse batteries).

The MX900 mouse + Apple's Wireless Keyboard works 100% now.

If you have any questions please feel free to ask!!!

:yes:

I've got an old Epox dongle that's spare since I upgraded my mac's dongle to a DBT-120 (for headset support).

Out of curiosity, I plugged it in.

Windows picked it up and installed its own drivers, and it's ready to go. I disable BT on my mac and turn the keyboard off, then go to add device on the PC. Turn the keyboard on, click search, click add, type in a pairing code, hit next, type in in on the keyboard. Bang, one working apple bluetooth keyboard.

Just to make sure, I rebooted. About 5 seconds after i'm presented the desktop, the keyboard's working.

Typing this with it now :)

  • 3 months later...

Thank God I found this post.

I was close to my harakiri. ;)

I'm having exactly the same problem (the PIN that doesn't show up to be typed).

I'm using in my notebook (Acer Aspire 2012WLMi) an internal BT module from Actiontec (BTM-200). My OS is WinXP SP2. The installed driver is HP 3.0.1.905 (great, except by this little mess); the driver supports HID (human interface device).

I already tried 3.0.1.914 and 4.0.1.2101, both patched (that license file issue)

Keyboard is OK, since I've tested:

1. in several Macs. Flawless. Mac OS generates a PIN (yes, this one is showed on screen) and you just type in the KB.

2. in a desktop PC, with the Microsoft built-in driver (SP2). Same thing as Mac: you choose a PIN, type in KB and everything is working.

3. in a desktop PC, with some other driver versions from Widcomm. Sometimes, driver don't find the KB. Sometimes, finds and allows choosing a PIN (but after typing, you get an error).

In cases [2] e [3] I've tested in a desktop PC with a Olympia Bluetooth dongle (CSR-like). I'm trying to update my Actiontec internal module to use Microsoft's built-in (and very limited) driver, but I can't even choose it from the "Update driver" list. I uninstalled the most recent driver version, but the "Generic Bluetooth Radio" doesn't show up.

Any help would be really appreciated. Thanks in advance.

  • 4 months later...

Hello.

I bought an Apple Wireless Keybaord and a D-Link DBT-120 USB bluetooth dongle to try to use the keyboard with Windows XP. I installed the drivers that came with the

The keyboard is not being recognized.

Can anyone guide me through the proper steps to get the keyboard working?

Thanks,

Avi

Actually, I tried the procedure quoted below, and the Bluetooth Device Manager finds the keyboard, and I get the Add Bluetooth Device Wizard "Windows is Installing Your Device." Then I click finish. But the keyboard doesn't work, and when I close and reopen the Bluetooth Devices control panels, the keyboard does not show up.

Any thoughts??

Thanks,

Avi

I've got an old Epox dongle that's spare since I upgraded my mac's dongle to a DBT-120 (for headset support).

Out of curiosity, I plugged it in.

Windows picked it up and installed its own drivers, and it's ready to go. I disable BT on my mac and turn the keyboard off, then go to add device on the PC. Turn the keyboard on, click search, click add, type in a pairing code, hit next, type in in on the keyboard. Bang, one working apple bluetooth keyboard.

Just to make sure, I rebooted. About 5 seconds after i'm presented the desktop, the keyboard's working.

Typing this with it now :)

  • 1 month later...

Could someone please comment as to whether the "caps lock" led works when using with a PC? (I read somewhere that the Apple Bluetooth does have an onboard caps lock LED...can't say, I've not seen one but I want to buy one because of the small footprint).

Any other comments, specifically....

the keyboard feel

what sucks? (eg I've seen some comments that the keys are too close together etc)

are drops frequent?

Also is the general consensu to go with the D-Link bluetooth adapter?

Many thanks in anticipation.

Hank McSpank

[Yank it, crank it & then rip the knob off]

Im using bluetooth with XP but seem to be having trouble with the Apple BT wireless keyboard pairing.

Im using the D-Link 120 dongle.

Everytime I restart windows i need to pair it again or else it won't work. The keyboard also needs to be switched on and off before re pairing.

Windows recognizes the keyboard after booting but it won't establish two way communication to be able to type. It shows the icon of a checkmark instead of the usual two green arrows and two way comm in widcomm.

It works flawlessly if I dont restart.

Any ideas how to make it work????

Hi!

I've succeeded in getting the Apple Wireless Keyboard to work on XP. Thanx to gunpowda and other helpful posts!

I thought I'd share some tips... It wasn't easy... :rolleyes:

I've been using the wireless keyboard for a couple of days and it works extremely well. Here's what ya get:

  1. Keyboard auto-pairs invisibly before XP login. It just works. No futzing after each restart (that would have been a deal-killer)
  2. Caps lock light works correctly. All keys work, except the 4 multimedia keys top right. Haven't looked into that yet.
  3. In BIOS screens and other very early startup events, the bluetooth of course isn't running yet... :)
  4. So smooth. Nice and fast to type on. Quiet action. No interference or stickyness despite all the other wireless gear I've got running.

This is NOT a definitive how-to, but might inspire...

I'm using a fairly new Bluetooth USB adapter: "Trust Bluetooth 2.0 EDR USB Adapter, BT-2200Tp"

All the new Widcomm/Broadcom bluetooth stacks (versions 4.1+ and 5.0+) hit you with the grayed out pairing box Gunpowda posted about. It's a brick wall, don't bother trying to get around it.

You need an old Widcomm driver. Version 1.4 did the trick for me, but 1.3 and earlier may work.

1.4 finds the keyboard and prompts you with multiple choices for pairing: autopairing, choose PIN, et c.

Get to that screen and you're golden.

Driver repository: The GSM-HOSTING forum is great for pointers to very old (and v. recent) drivers.

http://forum.gsmhosting.com/vbb/showthread.php?t=106274

All the best -R.

Thanks everyone for your effort. I'm replying this post using apple wireless keyboard.

I'm glad i saw this post and do the right thing beofore i stepped out to buy BT adapter.

I'm using windows xp sp2 and DBT-120 adapter. The main issue i encounter is still replacing the MS BT driver with the widcomm driver come with DBT-120.

I found a good cocument teaching you how to:

http://www.e-beam.com/support/Switching_fr..._to_WIDCOMM.pdf

However, I have to do the switching driver thing in "safe mode" . Otherwise, the widcomm driver won't show up in the stack when i update the MS BT driver.

Now, everything works very good. :D

everyone ....strange things happened here.

MS BT generic driver seems working better than widcomm~~ :o

The thing is that i found the keyboard sometimes worked but sometimes didn't when i restarted the computer. I have to mannually disconnect and connect again.

Therefore i decided to uninstall widcomm driver and restart and then reinstall again and see if it can automatically get connected every time i restart.

And then of course the windows generic driver took place aftr i uninstall widcomm and restart the computer.

Then i suddenly had the idea that why don't i just give the generic driver a try before i reinstall widcomm driver and replace MS BT driver.

To my surprise, it works. Now i felt stupid that i spent lots of time yesterday just trying to figure out how to replace it with widcomm. :D

Hello all.

I am using my Apple Keyboard with the new drivers without having to revert to the old drivers.

Its very easy. It took me a while to figure out how, but here is how.

With the regedit modify these two values.

HKEY_CURRENT_USER\Software\Widcomm\BtConfig\General

Set

PinCodeWord

To a value of

1111

Set

UseFixedPin

To a value of

1

Then attempt pairing.

Whne you get to the greyed PIN screen on the Apple Keyboard type

1111

Then Press the Return key on the Apple keyboard

Voila paired.

I have attempted to try other ways subsequentl, but I could never figure out how to UNPAIR the keyboard.

BeDammit

Ok, my UK Mac bluetooth keyboard seems to work just fine with my microsoft bluetooth dongle on XP - nothing special to do ....it just worked.

BUT I have a simple key mapping problem that's driving me potty. ....

by using a british keyboard listed under regional & language input languages, I can either have my ? key mapped to it's correct key (ie above the number 3) BUT unfortunately the @ and " symbols are swapped

OR

by using a US keyboard listed under regional & language input languages, I can have the @ and " symbols on their correct keys BUT then I get a # instead of a pound sign!!

I can't seem to work out a way to get the ?, @ and " symbols on their correct keys! (& even if I did, where would the hash key be?!)

Edited by HankMcSpank
  • 1 month later...

Hello all.

I would like to thanks BeDammit for his brilliant solution.

I' ll add some extra information to help people flawless set up their Apple Bluetooth keyboard on Windows XP.

1. Press Win Start button, choose Run and then type regedit and press enter to access windows registry editor.

2. Into the registry editor search for and select -> HKEY_CURRENT_USER\Software\Widcomm\BtConfig\General

3. Set the key 'PinCodeWord' to a decimal value of 1111

4. Set the key 'UseFixedPin' to a decimal value of 1

5. Then attempt pairing. When you get to the greyed PIN screen type 1111 using OTHER keyboard THAN Apple Bluetooth keyboard.

6. Press the Return key on the Apple keyboard.

7. Enjoy your nice Keyboard.

I think this one is the best solution cause you don't have to mess with windcomm driver version.

Thanks again BeDammit.

Edited by dongaspa
  • 2 weeks later...

Hello to all,

Yeepee I also manged to get my Apple wireless Keyboard to work on my PC very well (4hours non-stop thought).

For info I have a BlueTooth USB Dongle running WIDCOMM drivers ver 1.4.2.8

I would just like to add some more info in there :

- 1

Keyboard is OK, since I've tested:

1. in several Macs. Flawless. Mac OS generates a PIN (yes, this one is showed on screen) and you just type in the KB.

2. in a desktop PC, with the Microsoft built-in driver (SP2). Same thing as Mac: you choose a PIN, type in KB and everything is working.

3. in a desktop PC, with some other driver versions from Widcomm. Sometimes, driver don't find the KB. Sometimes, finds and allows choosing a PIN (but after typing, you get an error).

- First of all I've never did install a BlueTooth device before that so I would like to add an important step there.

About point n?2 : you have to use 2 Keyboards, for sure you need your Apple Wireless Keyboard(AWKB) + another one that is working well to type in the PIN when pairing.

About point n?3 : I had exactly this problem but there is a solution after a reboot only when you choose to add a new Bluetooth device, just before clicking on detect, turn on your AWKB, it should be detected properly else go back then turn off your AWKB then try again until it detects your AWKB.

As soon as it is detected do not wait for the search for new devices to end : select the Apple keyboard in the list of detected devices then hit next as speed as possible.

You're now on the screen where you have to pair your AWKB to the computer, you have to be quick (i tried many timings believe me) remove the random number and enter with your other keyboar1111 i>then right after clicking on the button to start the pairing use your Apple Wireless KB to blind inpu1111 Enteri> it should detect it.

If you still have problems I noticed that it's better to input the digits from the numpad on the AWKB (because you have to hold shift to access other digits).

For some reason on some computers the Enter key either is the one from the numpad either it is the main Enter key.

2 - It's important to enter something different that 0000 if you have to login using ctrl+alt+suppr. because you won't be able to put that value in PinCodeWord. I also want to add that PinCodeWord is a Dword value you have to create.

3 - I found a very interesting program named autohotkey (http://www.autohotkey.com/) this one is a little jewel.

Scriptable remapping of all keyboards keys !! Woohoo

You can even have it to turn scripts to executables that mean you don't even have to install the soft to benefit of the remapping.

For now I remapped :

F13 to launch an app

F14 F15 F16 are Mute | Vol- | Vol+

I even phisically switch the F buttons with the Vol buttons so the illusion of controlling sound is perfect.

There's also a small OnScreenDisplay that pops up to show you the volume status each time you push Vol+ or Vol-. I told you thatthing was sweet !!!

= (numpad one) still nothing

Hope it helps,

Answer here if you want to test the my key mapping I'll put the exe online.

Edited by zerofil
  • 1 year later...
  • 3 weeks later...
  • 3 months later...
Hello all.

I would like to thanks BeDammit for his brilliant solution.

I' ll add some extra information to help people flawless set up their Apple Bluetooth keyboard on Windows XP.

1. Press Win Start button, choose Run and then type regedit and press enter to access windows registry editor.

2. Into the registry editor search for and select -> HKEY_CURRENT_USER\Software\Widcomm\BtConfig\General

3. Set the key 'PinCodeWord' to a decimal value of 1111

4. Set the key 'UseFixedPin' to a decimal value of 1

5. Then attempt pairing. When you get to the greyed PIN screen type 1111 using OTHER keyboard THAN Apple Bluetooth keyboard.

6. Press the Return key on the Apple keyboard.

7. Enjoy your nice Keyboard.

I think this one is the best solution cause you don't have to mess with windcomm driver version.

Thanks again BeDammit.

Thanks a lot dongaspa and BeDammit,

I tried for couple of hours to get the keyboard paired, I checked many internet forums until I got to this one.

I did exactly as in the instructions and voila! It works!

I'm extremely happy I got it working, I really love this keyboard for its size, design and functionality.

There is one more step which could be added to the instructions: after changing the registers' values I had to reboot

before successfully pairing the keyboard. But maybe this is common knowledge already :).

By the way, my configuration is Windows XP pro + SP2 and a Belkin BT dongle (driver version 5.0.1).

I should go now to sleep, its 1 a.m. but at least I solved the problem :).

thanks again,

AdiVio

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • FINALLY a rare comment from someone who understands the industry. The level of clue essness in the comments in every article on Neowin is astounding.
    • The comment about clock speeds not changing is actually not really true. Due to aggressive power management, clock speeds on an idle system are lower now than they have been in decades. It isn't uncommon for a laptop to be hovering right around 1GHz if it isn't working on anything. Yes you right that more work gets done with each cycle, but you are still dealing with a nearly 5x difference between low and high power states, which can change how snappy the interface feels. I totally agree with you about the action center and other Windows UI elements taking a shameful amount of CPU cycles to do basic functions, but I see that as a separate conversation. While I do agree with the "don't sweep that under the rug" concern, I also don't want to get into a debate about what things deserve a boost or not. In my opinion, boost all the things, get the full value from your CPU. Keep in mind, we are talking about milliseconds of boosting, it isn't meaningfully going to change power consumption.
    • Windows 11 gets better widgets, new Screen Tint feature, and more in the latest build by Taras Buria While we usually cover Experimental and Beta builds together, this week's Beta updates are worth a separate article, as they offer more changes and new features than the other build. If you are a Windows Insider with a computer enrolled in the Beta Channel, you can download build 26220.8680 or build 28020.2298 (26H1). Today's release introduces long-anticipated improvements to Windows Widgets, a new display accessibility feature, File Explorer, and more. [Widgets] We're working to make Widgets feel less distracting and overwhelming by making the experience quiet by default. To do this, we're releasing a new set of default settings designed to reduce unexpected alerts and visual interruptions. These changes include: Disabling Open on hover by default Turning off Taskbar badging by default Opening to widgets experience on first launch Placing Weather as the only default widget on the lockscreen Restricting the number of Taskbar alerts that can be sent daily Limiting Taskbar alerts until you choose to open and engage with the Widgets experience As we continue to make Widgets feel less distracting, we've also made a small but meaningful visual update to taskbar badging. For those that have taskbar badging on, the badge color will now match your Windows accent color instead of always appearing red, reducing the sense of urgency that something needs your immediate attention. However, we still want it to be easy to find missed information so we now support badges on the icons in the Widget navigation bar that can show you the number of missed alerts from that specific dashboard; and badges clear automatically when you leave a dashboard, making it easy to track what's new. And if you don't want badges at all in your navigation bar, there's a setting to turn them off. We're also quieting down a user's experience based on their level of engagement, so that existing users also have a less distracting experience. For example, a user who barely engages with Widgets and would benefit from having the experience quieted down with taskbar badging turned off as it is for new users who experience it as quiet by default, as compared to a user who highly engages with Widgets and likely has their settings set to a state that works best for them and don't need some adjustments. You can also easily turn features like Taskbar badging on or off through Widgets settings, which is now a full screen experience that's easier to read. In pursuit of memory savings across the system, Widgets also now leverages device characteristics and user behavior patterns to optimize memory use. This includes things like a smaller default memory footprint, giving back memory faster when not in use, and limiting pre-launch on devices with lower memory capacity. Please share your feedback to let us know how these changes are working for you or if you encounter any issues with your quieter Widgets experience. Feedback: Share your thoughts in Feedback Hub (WIN + F) under Widgets. [Accessibility] New accessibility setting: Screen tint (also available in the 26H1 build) We're introducing screen tint, a new accessibility setting that applies a color overlay across your entire display, softening its intensity so it's easier on your eyes throughout the day. If bright, saturated screens leave you with tired or sensitive eyes by the end of a long session, screen tint can help. To get started, open Settings > Accessibility (or press Win + U) and look for screen tint under the Vision section. From there you can: Pick from six preset colors or choose a custom color of your own. Adjust the tint strength slider from a subtle wash to full intensity. Night light warms your display to reduce blue light that can interfere with sleep. Screen tint reduces overall screen intensity to ease eye fatigue and light sensitivity during the day. They tackle different problems and you can use both at the same time, one working on warmth and the other on intensity. Note that turning on screen tint will disable color filters, and vice versa. If you currently rely on color filters, you may need to keep screen tint turned off. [Windows Magnifier] Magnifier now gives you more control over how you zoom. You can type an exact zoom percentage directly in the magnifier toolbar to land on precisely the level you need. We've also added preset step increments (5%, 10%, 25%, 50%, 100%, 150%, 200%, and 400%) to the Settings dropdown, so you can jump to common levels in a single click. Whether you need a subtle boost or a dramatic close-up, Magnifier adapts to how you want to zoom. Feedback: Share your thoughts in Feedback Hub (WIN + F) under Accessibility > Magnifier [Input] Update: The emoji panel (Windows key + period (.)) now uses GIPHY as the GIF provider, delivering a smoother GIF browsing and sharing experience following the deprecation of Tenor. [Remote Recovery Management] Adding recovery remote management plug-in for extending WinRE management capabilities for MDM providers [File Explorer] The address bar now supports paths containing double backslashes and quotation marks (for example, C:\Users\user or "C:\Users\user"), improving compatibility with a wider range of inputs. Improved performance when mounting large ISO files by preventing File Explorer from becoming unresponsive during SmartScreen checks. The address bar suggestion dropdown is more reliable and now consistently closes after an item is selected. This update addresses an issue on File Explorer Home where OneDrive files could appear duplicated in the Favorites section. This update includes several refinements to the Rename experience: Addresses an issue where text was repeatedly selected when renaming items in folder views. Addresses an issue where case-only name changes were not immediately reflected in folder views for items stored locally or in the cloud. [Windows Update] If you were seeing error 0x800f0843 when attempting to install the previous update, that should be resolved now. [Other] - 26H1-only Task Scheduler will now persist column width adjustments in task list view across sessions. You can find the release notes for build 26220.8680 here and build 28020.2298 here.
    • Microsoft releases big Windows 11 25H2, 24H2 Release Preview with Recovery, Update features by Sayan Sen Microsoft has released today new Release Preview channel builds for Windows 11 Insiders. The new builds, 26100.8728 and 26200.8728, are for Windows 11 24H2 and 25H2 flighters, respectively. Meanwhile 26H1 flighters get 28000.2333. The new builds include new features related to Windows Update, Recovery, and more. The full changelogs, which are quite long today, are given below. First up we have for Builds 26200.8728 and 26100.8728: Gradual rollout This section highlights some new features and enhancements for Windows 11 PCs, including AI-powered capabilities, continuous innovation, and performance improvements. [Point-in-time restore for Windows] New! This flexible recovery feature helps you quickly roll back your PC, including apps, settings, and personal files, to a recent automatic restore point. It helps reduce downtime and simplifies troubleshooting when issues occur. To learn more, see Point-in-time restore for Windows. [Windows Update] New! A calendar experience in Windows Update settings (Settings > Windows Update) lets you pause updates by choosing an end date, for up to 35 days. You can extend the pause by selecting a different end date and re-pause updates as needed. [Widgets] New! A quieter, more focused Widgets experience helps reduce interruptions and improves default settings and notification controls: Reduce distractions: Widgets no longer open on hover. Notifications and taskbar badges are minimized by default, and badges use colors that match your Windows accent. Simpler: Open to the Widgets dashboard by default on first use. New users see a simplified experience on lock screen with Weather as the only default widget. Customize: Configure Widgets the way you want by selecting Settings in the navigation bar, then changing any default settings. Stay informed: Dashboard icons show the number of alerts, and badges clear automatically when you leave a dashboard. Adjusted defaults: Some default settings are preserved based on usage, while others adjust to reduce interruptions. Performance improvements: This update provides improved reliability, responsiveness, and visual quality across the Widgets experience. [Accessibility] New! This update makes your screen easier to see and helps you customize your zoom experience: Screen tint: Apply a full-screen color overlay to help reduce eye strain and improve readability. Choose from preset tint options, adjust intensity, or turn it on automatically. Find this feature in Settings > Accessibility. Magnifier: Enter a zoom percentage directly and change it in increments in the Magnifier window for more precise, flexible control. Magnifier settings menu: Modify zoom increments directly from the Magnifier bar instead of navigating to Windows Settings each time. [File Explorer] When you hover over a file in File Explorer Home, commands such as Open file location and Ask Copilot appear as quick actions. This experience is now supported for work and school accounts (Entra ID). This feature isn't available in the European Economic Area. The address bar now supports paths containing double backslashes and quotation marks (for example, C:\Users\user or "C:\Users\user"), improving compatibility with a wider range of inputs. The address bar suggestion dropdown is more reliable and now consistently closes after an item is selected. This update addresses an issue on File Explorer Home where OneDrive files could appear duplicated in the Favorites section. This update includes several refinements to the Rename experience: Addresses an issue where text was repeatedly selected when renaming items in folder views. Addresses an issue where case-only name changes were not immediately reflected in folder views for items stored locally or in the cloud. [Bluetooth] This update improves reliability and performance when connecting to and using Bluetooth devices: New! Windows now keeps the microphone mute state in sync between the audio mixer and the Hands-Free Profile (HFP) for a more consistent experience with Bluetooth headphones with mute buttons or indicators. Device compatibility: Improves compatibility with certain Bluetooth audio devices, helping AirPods appear faster in pairing mode and improving microphone reliability on Beats Studio Pro headphones. Bluetooth audio stability and quality: Improves Bluetooth audio stability with certain PC manufacturer drivers (error code 0x9F). Improves Bluetooth audio quality and reliability for voice calls when using classic audio devices with the Hands-Free Profile (HFP). Improves reliability of LE Audio streaming after a connection is lost and restored. Reduces time for LE Audio accessories to start playing audio while using the microphone. Device management: Bluetooth device removal is now more reliable when the Bluetooth radio is disabled or changed after pairing, reducing occurrences of the "Remove failed" message. Settings experience: Improves stability when using the Bluetooth & devices settings page for a smoother, more consistent experience. Connection reliability and responsiveness: Reduces the time it takes for classic Bluetooth audio devices to reconnect after Windows resumes from hibernation. Improves reliability when LE Audio accessories disconnect, such as when another device (for example, a phone) connects. [Bluetooth and Phone Link] This update improves audio routing for calls made through a connected phone: When an outgoing call is dialed from a paired phone, audio remains on the phone while ringing and transfers to the PC only when the call is answered from the PC. When Do Not Disturb is enabled on Windows, incoming call audio from a paired phone no longer rings on the PC. [Voice access and voice typing] New! You can now use voice access and voice typing in French, German, and Spanish. As you speak, your PC improves your text in real time. It corrects grammar, punctuation, and recognition errors, and helps improve clarity, even in the presence of background noise. This makes dictation smoother and reduces the need for manual edits. Available on Copilot+ PCs. [Audio] This update improves the reliability of the inbox HD Audio driver. [Taskbar] This update improves the reliability of invoking the Start menu when clicking the left edge of the taskbar when icons in the taskbar are left-aligned. [Emoji panel] The emoji panel (Windows key + period (.)) now uses GIPHY as the GIF provider, delivering a smoother GIF browsing and sharing experience following the deprecation of Tenor. [Networking] This update includes networking improvements for virtualized environments. Confidential Virtual Machines (CVMs) now use SR-IOV hardware acceleration by default for improved network throughput, and a configuration issue in nested Hyper-V virtualization network setup has been corrected to ensure reliable VM network provisioning. This update improves the reliability of the Windows networking stack. It reduces bug checks (blue screen errors) related to Wi-Fi power and improves cellular (WWAN) connectivity, including support for IPv6 VPNs. Compatibility with third-party VPN software and SR-IOV configurations on server hardware is also improved. Network adapter settings and bindings are now preserved across OS upgrades. [Printing] New! New printer installations use Internet Printing Protocol (IPP) by default when supported, simplifying setup and improving reliability. To control this behavior, use the toggle in Settings > Bluetooth & devices > Printers & scanners > Default install printers using Windows Ready Print. [Windows Subsystem for Linux (WSL)] This update improves usage of WSL in mirrored networking mode with VPNs. [Display and graphics] Improves reliability of rendering content while scrolling for certain apps spanning across multiple monitors. Improves reliability and persistence of applying color profiles. [Location services] This update changes how some location settings are displayed in Settings > Privacy & Security > Location to help with clarity. When location services are turned off, settings like Default location and Allow location override do not immediately apply, since location information is not given to apps or services. These settings are now greyed out when location services are off to reduce confusion over when they take effect. [Search] This update improves the reliability of setting Search-related group policies. [Input] New! You can now customize the size of the right-click zone in Settings > Bluetooth & devices > Touchpad. Choose from default, small, medium, or large to control how much of the bottom-right corner responds to a single-finger right-click. This setting is only available on touchpads with a pressable surface. If your device manufacturer provides customization through their app, a Custom option appears to reflect those settings. This update also improves recognition of English characters when using Japanese handwriting. [General Reliability] This update makes underlying changes to help improve explorer.exe reliability, including addressing reliability issues on the login and lock screens related to the use of third-party credential providers, reducing the probability of taskbar icons appearing as blank gray placeholders, improving reliability of navigating to File Explorer Home during OneDrive sync, improving explorer.exe reliability when switching between multiple desktops, improving app launch reliability when shell extensions are installed, and addressing reliability issues related to acrylic blur effects in Start menu, Settings, and the lock screen. Normal rollout This non-security update includes quality improvements. The following summary outlines key issues addressed by the KB update after you install it. Also, included are available new features. The bold text within the brackets indicates the item or area of the change. [Secure Boot] 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. [Authentication] This update improves Netlogon secure channel connections between domain controllers, enabling successful connections from member servers to domain controllers set up before 2025. [Networking] This update improves how your device connects to shared network resources. Connections used by apps and system features, such as the NetUseAdd function, now work more reliably, including unauthenticated (null session) connections. [Start Menu] This update improves the Start menu experience, allowing newly installed or removed apps to appear without requiring sign-out or restart. This mainly affects apps that create a Start menu folder with multiple shortcuts. [Taskbar] This update improves notification badge display across your apps. Notification counts and badge visuals now update correctly, helping you stay up to date with new activity. Up next we have build 28000.2333: Gradual rollout Windows 11 PC experiences This section highlights some new features and enhancements for Windows 11 PCs, including AI-powered capabilities, continuous innovation, and performance improvements. [Magnifier in Windows] New! Magnifier now provides clearer and more consistent announcements when working with a screen reader. You'll hear helpful announcements when you zoom in or out, switch views, turn color inversion on or off, or turn Magnifier On or Off. This makes it easy to stay oriented while you work. New! Magnifier now supports magnification of permitted protected content. This update improves smoothness when moving Magnifier in lens mode. [Task Manager] New! Task Manager now offers improved visibility into NPU usage on PCs with an NPU. New optional NPU and NPU Engine columns are available on the Processes, Users, and Details pages, along with NPU Dedicated Memory and NPU Shared Memory optional columns on the Details page. Neural engines that are part of a GPU now appear on the Performance page, providing a more complete view of AI-related activity. A new optional Isolation column on the Processes and Details pages shows which apps are running in an AppContainer. You can add any of the new columns by right-clicking a column header in Task Manager and selecting them from the menu. This update improves CPU speed display on the Performance page of Task Manager for VMs, so it doesn't show higher than unexpected numbers after resuming from hibernate. [Camera] New! Windows 11's Multi-App Camera feature allows multiple applications to access your camera stream at the same time. Basic Camera mode in Windows 11 enables simplified camera functionality, useful for troubleshooting or improving stability when your camera is not working correctly. Enterprise admin can now set Multi-App Camera mode or Basic Camera mode through Group Policy, under Computer Configuration > Administrative Templates > Windows Components > Camera > Configure Camera Options. [Windows Setup] New! You can now choose a custom name for your user folder on the Device Name page during Windows setup. The updated experience makes it easier to select a custom name during setup only. If this step is skipped, Windows uses the default folder name and continues setup as usual. User folder names must follow standard Windows naming requirements. [General Performance] This update accelerates app launch and core shell experiences such as Start menu, Search, and Action Center. [Personalization] This update improves: Color selection accuracy when adjusting your accent color to match your wallpaper when the automatic accent color selection is enabled in Personalization settings. Wallpaper persistence reliability across restarts and upgrades, including better support for large-resolution wallpapers and other scenarios to prevent solid color wallpaper fallback. [Windows Hello] This update improves: This update optimizes the Windows Biometric service (WinBio) to help improve performance when your device resumes from Modern Standby. This update reduces unexpected authentication blocks in Windows Hello Enhanced Sign-in Security by resolving missing secure enrollment metadata. This update improves sign-in behavior on the lock screen and sign-in screen. When Windows Hello face or fingerprint is set up and available, it is now the default sign-in method every time you sign in, even if you used a different method previously. If you need to use your Windows PIN instead and use it three times in a row, Windows will stay with PIN until you switch to another sign-in method. [Windows Search Box] Windows Search will now find and prioritize files with as few as two characters. [Storage] The dialog box for creating a Dev Drive now supports specifying the size in gigabytes (GB) instead of only megabytes (MB). This option is also available when resizing volumes in Settings > System > Storage. In Settings > System > Storage, you now see a User Account Control (UAC) prompt only when you choose to view temporary files, instead of immediately when opening the page. [USB] This update improves reliability for displays attached to USB4 docks and hubs. These displays now light up more consistently, particularly when coming out of standby. The USB3 stack is updated to have additional resiliency and recovery measures in place against certain unexpected hardware faults and conditions. Users will experience higher reliability with USB devices. [Sensors] This update improves resiliency against apps that could keep the sensor hub powered on and drain power, impacting battery life. [Human Interface Device (HID)] This update improves battery life related to the HID and Input stack for failed HID devices. Power hygiene is also improved against applications that might initiate HID transfers during standby. [Input] The update improves: Reliability of the touch keyboard on the sign-in screen, including when entering or changing a password. Reliability of explorer.exe when closing the input switcher. Performance when opening or navigating to clipboard history. [Fonts] The Times New Roman font family is updated to improve the rendering of combining diacritical marks across Greek and Cyrillic scripts. This update provides more accurate and visually consistent text by addressing mark positioning issues. These changes improve readability, reduce rendering inconsistencies, and better support global language users working with Greek and Cyrillic content. [Task Scheduler] Task Scheduler now saves column width adjustments in task list view across sessions. [Desktop icons] This update improves reliability of loading desktop app shortcuts. [Microsoft Store] This update includes underlying changes that improve download performance and bandwidth usage. This update improves error reporting when downloads fail due to Windows Update group policy settings being enabled. [Reliability] This update improves Windows reliability on the sign-in and lock screens, in File Explorer, when using touch gestures on touchscreen devices, and when changing themes in Settings. Normal rollout This non-security update includes quality improvements. The following summary outlines key issues addressed by the KB update after you install it. Also, included are available new features. The bold text within the brackets indicates the item or area of the change. [Authentication] This update improves Netlogon secure channel connections between domain controllers, enabling successful connections from member servers to domain controllers set up before 2025. [BitLocker] This update improves BitLocker testing reliability by ensuring the required files are available for the BitLocker Drive Encryption USB BIOS Logo Test. You can find the blog post for builds 26100.8728/26200.8728 here and build 28000.2333 here.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      502
    2. 2
      PsYcHoKiLLa
      172
    3. 3
      +Edouard
      163
    4. 4
      Steven P.
      86
    5. 5
      ATLien_0
      77
  • Tell a friend

    Love Neowin? Tell a friend!