Insider Windows 11 Insider Canary and Dev build 26100.1 (24H2) - April 3


  • Staff
UPDATE 4/26:

UPDATE 4/19:


 Windows Blogs:

Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 26100 to the Canary and Dev Channels.

The Canary and Dev Channels receiving the same builds is only temporary. During the times in which the Canary and Dev Channels are on the same builds (e.g. Build 26100), the window is open for Insiders in the Canary Channel to switch to the Dev Channel. In the near future, the Canary Channel will jump to higher build numbers and the window will be closed so make your choice on which channel to be in soon!


NOTE: Some features may begin rolling out to the Canary Channel first before the Dev Channel even if the two channels have the same build.

What’s new in Build 26100

Changes and Improvements

[General]

  • [REMINDER] The build watermark at the lower right-hand corner of the desktop is not present in this build and will return in future Insider Preview builds. This is part of our normal process preparing Windows 11, version 24H2 for releasing to customers later this year – but does not mean we’re done. Windows 11, version 24H2, will be this year’s annual feature update. As mentioned here, Windows 11 will have an annual feature update cadence that releases in the second half of the calendar year.

Fixes for known issues

[General]

  • Made another fix to address the issue causing shutdown and hibernate to not work in the latest builds.
  • Fixed an issue resulting in some Insiders seeing error 0x80240067 when trying to download app updates from Microsoft Store or Windows updates in Settings in the latest builds.

[Copilot in Windows*]

[Windowing]

  • Fixed a DWM crash impacting some Insiders in the latest flights (this could result in you seeing your screen flash black).

Known issues

[General]

  • [IMPORTANT NOTE] We are investigating reports that some Windows Insiders in the Canary and Dev Channels are stuck on Build 26040 or Build 23620. The investigation is ongoing, however if you are impacted by this and really want to get onto the latest build in the Canary or Dev Channel today – you can download the latest ISO here and do a clean install and opt your device back into flighting in the Canary or Dev Channels.

[Copilot in Windows*]

  • [ADDED 4/12] We are aware of reports by Insiders in the Canary and Dev Channels that Copilot is auto-launching unexpectedly after restarting their PCs. We hope to have a fix for this issue soon and is unrelated to the auto-launching experience we tried out with Insiders in the Canary and Dev Channels in early February which we stopped rolling out in March.
  • Voice access does not work reliably with the updated Copilot in Windows experience that introduces the ability for Copilot to act like a normal application.
  • Using Windows Ink to write in Copilot will not work with the updated Copilot in Windows experience that introduces the ability for Copilot to act like a normal application window.
  • When Copilot in Windows is docked and resized to a large width, Copilot does not always fill the width of the panel. Resizing Copilot usually fixes this issue.

For developers

You can download the latest Windows Insider SDK at aka.ms/windowsinsidersdk.

SDK NuGet packages are now also flighting at NuGet Gallery | WindowsSDK which include:
These NuGet packages provide more granular access to the SDK and better integration in CI/CD pipelines.

SDK flights are now published for both the Canary and Dev Channels, so be sure to choose the right version for your Insider Channel.

Remember to use adaptive code when targeting new APIs to make sure your app runs on all customer machines, particularly when building against the Dev Channel SDK. Feature detection is recommended over OS version checks, as OS version checks are unreliable and will not work as expected in all cases.

Reminders for Windows Insiders

  • The Canary and Dev Channels receive builds with features and experiences that may never get released as we try out different concepts and get feedback. Features may change over time, be removed, or replaced and never get released beyond Windows Insiders. Some of these features and experiences could show up in future Windows releases when they’re ready.
  • Many features in the Canary and Dev Channel are rolled out using Control Feature Rollout technology, starting with a subset of Insiders and ramping up over time as we monitor feedback to see how they land before pushing them out to everyone in these channels.
  • As the Canary and Dev Channels receive the same builds, some features may begin rolling out to the Canary Channel first before the Dev Channel.
  • While the Canary Channel is now on Windows 11, version 24H2, this is just temporary. At some point in the future, the Canary Channel will jump ahead to receiving new builds not matched to any specific release in a higher build series.
  • To get off the Canary or Dev Channel, a clean install of Windows 11 will be required. As a reminder – Insiders can’t switch to a channel that is receiving builds with lower build numbers without doing a clean installation of Windows 11 due to technical setup requirements.
  • The desktop watermark shown at the lower right corner of the desktop is normal for these pre-release builds.
  • Check out Flight Hub for a complete look at what build is in which Insider channel.
  • Copilot in Windows* in preview is being rolled out gradually to Windows Insiders in select global markets. The initial markets for the Copilot in Windows preview include North America, United Kingdom and parts of Asia and South America. It is our intention to add additional markets over time.
Thanks,
Amanda & Brandon


 Source:



Check Windows Updates


UUP Dump:

64-bit ISO download:

ARM64 ISO download:

 
Last edited:
Yes, keep it.
Thanks for letting me know. Now I just need for Macrium to finish so I can give it a try on my new desktop.
 

My Computers

System One System Two

  • OS
    Windows 11 Canary Channel
    Computer type
    PC/Desktop
    Manufacturer/Model
    PowerSpec B746
    CPU
    Intel Core i7-10700K
    Motherboard
    ASRock Z490 Phantom Gaming 4/ax
    Memory
    16GB (8GB PC4-19200 DDR4 SDRAM x2)
    Graphics Card(s)
    NVIDIA GeForce GTX 1050 TI
    Sound Card
    Realtek Audio
    Monitor(s) Displays
    Samsung SAM0A87 Samsung SAM0D32
    Screen Resolution
    1920 x 1080
    Hard Drives
    NVMe WDC WDS100T2B0C-00PXH0 1TB
    Samsung SSD 860 EVO 1TB
    PSU
    750 Watts (62.5A)
    Case
    PowerSpec/Lian Li ATX 205
    Keyboard
    Logitech K270
    Mouse
    Logitech M185
    Browser
    Microsoft Edge and Firefox
    Antivirus
    ESET Internet Security
  • Operating System
    Windows 11 Canary Channel
    Computer type
    PC/Desktop
    Manufacturer/Model
    PowerSpec G156
    CPU
    Intel Core i5-8400 CPU @ 2.80GHz
    Motherboard
    AsusTeK Prime B360M-S
    Memory
    16 MB DDR 4-2666
    Monitor(s) Displays
    23" Speptre HDMI 75Hz
    Screen Resolution
    1920x1080
    Hard Drives
    Samsung 970 EVO 500GB NVMe
    Mouse
    Logitek M185
    Keyboard
    Logitek K270
    Browser
    Firefox, Edge and Edge Canary
    Antivirus
    Windows Defender
For any veterans of 0xc1900101 from past builds, any tips? Not sure why it's happening here now and not before, but I'm going to try a uupdump iso to see if that gets around it as they sometimes can.
 

My Computer

System One

  • OS
    Windows 11

My Computers

System One System Two

  • OS
    Windows 11 Canary Channel
    Computer type
    PC/Desktop
    Manufacturer/Model
    PowerSpec B746
    CPU
    Intel Core i7-10700K
    Motherboard
    ASRock Z490 Phantom Gaming 4/ax
    Memory
    16GB (8GB PC4-19200 DDR4 SDRAM x2)
    Graphics Card(s)
    NVIDIA GeForce GTX 1050 TI
    Sound Card
    Realtek Audio
    Monitor(s) Displays
    Samsung SAM0A87 Samsung SAM0D32
    Screen Resolution
    1920 x 1080
    Hard Drives
    NVMe WDC WDS100T2B0C-00PXH0 1TB
    Samsung SSD 860 EVO 1TB
    PSU
    750 Watts (62.5A)
    Case
    PowerSpec/Lian Li ATX 205
    Keyboard
    Logitech K270
    Mouse
    Logitech M185
    Browser
    Microsoft Edge and Firefox
    Antivirus
    ESET Internet Security
  • Operating System
    Windows 11 Canary Channel
    Computer type
    PC/Desktop
    Manufacturer/Model
    PowerSpec G156
    CPU
    Intel Core i5-8400 CPU @ 2.80GHz
    Motherboard
    AsusTeK Prime B360M-S
    Memory
    16 MB DDR 4-2666
    Monitor(s) Displays
    23" Speptre HDMI 75Hz
    Screen Resolution
    1920x1080
    Hard Drives
    Samsung 970 EVO 500GB NVMe
    Mouse
    Logitek M185
    Keyboard
    Logitek K270
    Browser
    Firefox, Edge and Edge Canary
    Antivirus
    Windows Defender
Does anybody get this problem with MS Store updates?
With the last 3 Canary/Dev builds 26085, 26090, 26100, if I use the ISO from UUPDUMP to update the system I cannot update some of the MS Store apps after the build is updated.
I get the messages below and there is no way to update those Apps.
The problem does not happen when I update the same systems with W.U. only when I use the ISO to update or update/repair in place.
I 'm trying to prevent downloading the same build over and over for different machines, but this problem forces me to use W.U. for every machine. 😝🤬
This problem does not happen if I use the same ISO to do a clean install, it only happens after an update from a previous Canary Build or an update/repair in place of the same Build.

1712187696229.png
 
Last edited:

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo Yoga 920
    CPU
    Intel I7-8550U
    Motherboard
    n/a
    Memory
    16GB
    Graphics Card(s)
    Intel Graphics UHD 620
    Sound Card
    Realtek High Definition Audio (SST)
    Monitor(s) Displays
    4k Touch screen
    Screen Resolution
    3480 x 2160
    Hard Drives
    512GB NVMe
Don't be surprised if you find yourself becoming a B tester.
To be honest, I don't give a :poop:!
I'm so done with this Insider cruft! I just do it cuz I'm a nosy bugger! 🤷‍♂️
 

My Computers

System One System Two

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    ASUS ROG Strix
  • Operating System
    Windows 11
    Computer type
    Laptop
    Manufacturer/Model
    ASUS VivoBook
To be honest, I don't give a :poop:!
I'm so done with this Insider cruft! I just do it cuz I'm a nosy bugger! 🤷‍♂️
When I became an Insider I did it for the excitement of being one of the first to test out new features so I could help find any problems before they were released to the general public. With what is being released lately the excitment isn't there anymore. For me the excitement has turned to seeing how many tries it takes to successfully update. I know I can always drop out by doing a clean install but I'm not ready to give up yet.
 

My Computers

System One System Two

  • OS
    Windows 11 Canary Channel
    Computer type
    PC/Desktop
    Manufacturer/Model
    PowerSpec B746
    CPU
    Intel Core i7-10700K
    Motherboard
    ASRock Z490 Phantom Gaming 4/ax
    Memory
    16GB (8GB PC4-19200 DDR4 SDRAM x2)
    Graphics Card(s)
    NVIDIA GeForce GTX 1050 TI
    Sound Card
    Realtek Audio
    Monitor(s) Displays
    Samsung SAM0A87 Samsung SAM0D32
    Screen Resolution
    1920 x 1080
    Hard Drives
    NVMe WDC WDS100T2B0C-00PXH0 1TB
    Samsung SSD 860 EVO 1TB
    PSU
    750 Watts (62.5A)
    Case
    PowerSpec/Lian Li ATX 205
    Keyboard
    Logitech K270
    Mouse
    Logitech M185
    Browser
    Microsoft Edge and Firefox
    Antivirus
    ESET Internet Security
  • Operating System
    Windows 11 Canary Channel
    Computer type
    PC/Desktop
    Manufacturer/Model
    PowerSpec G156
    CPU
    Intel Core i5-8400 CPU @ 2.80GHz
    Motherboard
    AsusTeK Prime B360M-S
    Memory
    16 MB DDR 4-2666
    Monitor(s) Displays
    23" Speptre HDMI 75Hz
    Screen Resolution
    1920x1080
    Hard Drives
    Samsung 970 EVO 500GB NVMe
    Mouse
    Logitek M185
    Keyboard
    Logitek K270
    Browser
    Firefox, Edge and Edge Canary
    Antivirus
    Windows Defender
I 'm trying to prevent downloading the same build over and over for different machines, but this problem forces me to use W.U. for every machine. 😝🤬
It's not that bad using Windows Update, not if you allow downloads from other PCs and update more than one machine at a time. I keep Task Manager open at the Performance tab and watch the network activity, with two machines downloading the same builds in WU I have seen one send updates to the other.

1712189789528.png
 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Beta as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, and Canary builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Lattitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Beta as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 4GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, and Canary builds as a native boot .vhdx.
It's not that bad using Windows Update, not if you allow downloads from other PCs and update more than one machine at a time. I keep Task Manager open at the Performance tab and watch the network activity, with two machines downloading the same builds in WU I have seen one send updates to the other.

View attachment 92462
The question remains, what is wrong with the UUPDUMP ISO update?
 

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo Yoga 920
    CPU
    Intel I7-8550U
    Motherboard
    n/a
    Memory
    16GB
    Graphics Card(s)
    Intel Graphics UHD 620
    Sound Card
    Realtek High Definition Audio (SST)
    Monitor(s) Displays
    4k Touch screen
    Screen Resolution
    3480 x 2160
    Hard Drives
    512GB NVMe
As I expected, the first try using W/U did a roll back. Now I'm going to try with an ISO as soon as UUPDump finishes.
 

My Computers

System One System Two

  • OS
    Windows 11 Canary Channel
    Computer type
    PC/Desktop
    Manufacturer/Model
    PowerSpec B746
    CPU
    Intel Core i7-10700K
    Motherboard
    ASRock Z490 Phantom Gaming 4/ax
    Memory
    16GB (8GB PC4-19200 DDR4 SDRAM x2)
    Graphics Card(s)
    NVIDIA GeForce GTX 1050 TI
    Sound Card
    Realtek Audio
    Monitor(s) Displays
    Samsung SAM0A87 Samsung SAM0D32
    Screen Resolution
    1920 x 1080
    Hard Drives
    NVMe WDC WDS100T2B0C-00PXH0 1TB
    Samsung SSD 860 EVO 1TB
    PSU
    750 Watts (62.5A)
    Case
    PowerSpec/Lian Li ATX 205
    Keyboard
    Logitech K270
    Mouse
    Logitech M185
    Browser
    Microsoft Edge and Firefox
    Antivirus
    ESET Internet Security
  • Operating System
    Windows 11 Canary Channel
    Computer type
    PC/Desktop
    Manufacturer/Model
    PowerSpec G156
    CPU
    Intel Core i5-8400 CPU @ 2.80GHz
    Motherboard
    AsusTeK Prime B360M-S
    Memory
    16 MB DDR 4-2666
    Monitor(s) Displays
    23" Speptre HDMI 75Hz
    Screen Resolution
    1920x1080
    Hard Drives
    Samsung 970 EVO 500GB NVMe
    Mouse
    Logitek M185
    Keyboard
    Logitek K270
    Browser
    Firefox, Edge and Edge Canary
    Antivirus
    Windows Defender
Wanted to try a uupdump iso to see if gets around 0xc1900101. I was surprised to hit this right away with the mounted iso:.

While it's true, it's also true that I not only have "Skip_TPM_Check_on_Dynamic_Update.cmd" in effect but also the extensive reg file from elsewhere on this site (BypassSecureBootCheck, etc). Anyone know why?

explorer_zBOkokS9y1.png
 

My Computer

System One

  • OS
    Windows 11
As I expected, the first try using W/U did a roll back. Now I'm going to try with an ISO as soon as UUPDump finishes.
Please let me know if you get problems with updating Apps from the MS store after updating with UUPDUMP ISO. 😎
 

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo Yoga 920
    CPU
    Intel I7-8550U
    Motherboard
    n/a
    Memory
    16GB
    Graphics Card(s)
    Intel Graphics UHD 620
    Sound Card
    Realtek High Definition Audio (SST)
    Monitor(s) Displays
    4k Touch screen
    Screen Resolution
    3480 x 2160
    Hard Drives
    512GB NVMe
Wanted to try a uupdump iso to see if gets around 0xc1900101. I was surprised to hit this right away with the mounted iso:.

While it's true, it's also true that I not only have "Skip_TPM_Check_on_Dynamic_Update.cmd" in effect but also the extensive reg file from elsewhere on this site (BypassSecureBootCheck, etc). Anyone know why?

View attachment 92463
Is that still a legacy BIOS PC?
Why is Secure Boot not available? I thought Secure Boot was available on any UEFI machine. 🤷‍♂️
 

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo Yoga 920
    CPU
    Intel I7-8550U
    Motherboard
    n/a
    Memory
    16GB
    Graphics Card(s)
    Intel Graphics UHD 620
    Sound Card
    Realtek High Definition Audio (SST)
    Monitor(s) Displays
    4k Touch screen
    Screen Resolution
    3480 x 2160
    Hard Drives
    512GB NVMe
Is that still a legacy BIOS PC?
Why is Secure Boot not available? I thought Secure Boot was available on any UEFI machine. 🤷‍♂️

It is Legacy. I'm baffled why the ISO method doesn't work. I even tried the appraiserres.dll swap, no-go.

Note that I never normally have to think about this, since I just use WU and Skip_TPM_Check_on_Dynamic_Update.cmd does its thing. Only went to the ISO because of the WU problem. Maybe it's the very same issue though just expressed in two different ways.
 

My Computer

System One

  • OS
    Windows 11
It is Legacy. I'm baffled why the ISO method doesn't work. I even tried the appraiserres.dll swap, no-go.

Note that I never normally have to think about this, since I just use WU and Skip_TPM_Check_on_Dynamic_Update.cmd does its thing. Only went to the ISO because of the WU problem. Maybe it's the very same issue though just expressed in two different ways.
It has been a while; I think MS blocked the Legacy BIOS several Canary Builds ago.
I cannot even Boot the installation media on a Legacy BIOS machine, because MS changed the bootmgr file to post a disk error when trying to boot. I replaced the file with an older one to work around the problem, but then it fails the same way when trying to boot the installed system.
I gave up using Legacy Bios with Canary 2 or 3 months ago.
 

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo Yoga 920
    CPU
    Intel I7-8550U
    Motherboard
    n/a
    Memory
    16GB
    Graphics Card(s)
    Intel Graphics UHD 620
    Sound Card
    Realtek High Definition Audio (SST)
    Monitor(s) Displays
    4k Touch screen
    Screen Resolution
    3480 x 2160
    Hard Drives
    512GB NVMe
It has been a while; I think MS blocked the Legacy BIOS several Canary Builds ago.
That would have made big news. You're not thinking of that POPCNT feature, right? That was one notable change a few months ago but only applied to CPUs that predated something like 2009, at least on the Intel side.

When you say that you haven't been able to use Canary builds, do you mean even on systems that had been working? Because that's all I've been dealing with. I don't have any recent experience on new installs.
 

My Computer

System One

  • OS
    Windows 11
That would have made big news. You're not thinking of that POPCNT feature, right? That was one notable change a few months ago but only applied to CPUs that predated something like 2009, at least on the Intel side.

When you say that you haven't been able to use Canary builds, do you mean even on systems that had been working? Because that's all I've been dealing with. I don't have any recent experience on new installs.
Yes, a system that has been working with older Canary and Dev Builds and still works with 22631 and 22635, it does not work with any of the latest Canary or Dev 26xxx.
POPCNT is not an issue it is a pretty old instruction added 17 years ago. 😉
 

My Computer

System One

  • OS
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo Yoga 920
    CPU
    Intel I7-8550U
    Motherboard
    n/a
    Memory
    16GB
    Graphics Card(s)
    Intel Graphics UHD 620
    Sound Card
    Realtek High Definition Audio (SST)
    Monitor(s) Displays
    4k Touch screen
    Screen Resolution
    3480 x 2160
    Hard Drives
    512GB NVMe

My Computers

System One System Two

  • OS
    22631.3593
    Computer type
    PC/Desktop
    CPU
    i5-11400F
    Motherboard
    Gigabyte
    Memory
    32GB
    Graphics Card(s)
    Geforce GT-1030
    Keyboard
    Logitech K400
    Mouse
    Logitech M720
    Internet Speed
    600 Mb
    Browser
    Edge
  • Computer type
    Laptop
    CPU
    Pentium N4200
    Motherboard
    ASUS
    Memory
    4GB
    Graphics card(s)
    Intel HD Graphics 505
    Sound Card
    HD Definition Audio Device
    Screen Resolution
    1366 x 768
    Mouse
    M510
    Internet Speed
    100Mb +
    Browser
    Edge
    Antivirus
    Windows Security
Yes, a system that has been working with older Canary and Dev Builds and still works with 22631 and 22635, it does not work with any of the latest Canary or Dev 26xxx.
POPCNT is not an issue it is a pretty old instruction added 17 years ago. 😉

That's so weird. I hope you can narrow why it is, but it can't strictly relate to legacy bios in general, since I most definitely don't have UEFI. The Bios Mode according to msinfo32 is Legacy.

On today's issue here with me, uh, I have no good explanation for any of it. I failed 6 times in the first half of the day and then stopped trying things because nothing was working. Late in the day I tried the WU one more time, but since I was sure it wouldn't work I deferred rebooting until pretty late tonight. As soon as I clicked reboot, it went to a type of screen that I don't quite recall seeing before, one that went from 0% to 100% pretty quickly but notably said that it was updating.

Did MS perhaps push some kind of compatibility fix late in the day given that the lone Known Issue is related to upgrades? If they did, I guess we'll hear about it tomorrow, but I have no other explanation for what happened after the reboot: it went through the rest of setup. In other words, it worked and didn't just bounce right back into Windows as it had done the first half dozen times today. I didn't change anything, so it feels more like MS did.
 

My Computer

System One

  • OS
    Windows 11
And, if that don't work, MS can take this Build and stick it where the sun don't shine! There's no way in hell I'm gonna run that lame-a$$ Explorer SDK!
Keep your knickers on!
 

My Computers

System One System Two

  • OS
    Windows 11 build 10.0.26635.3566 Beta
    Computer type
    Laptop
    Manufacturer/Model
    Dell Inspiron 14 5430
    CPU
    Intel i7-1355U
    Motherboard
    Dell 0GMW80
    Memory
    16GB
    Graphics Card(s)
    Intel Iris XE
    Sound Card
    Realtek
    Monitor(s) Displays
    Dell 14" and LG Ultrawide 26"
    Screen Resolution
    1920 x 1200 and 2560 x 1080
    Hard Drives
    Samsung 990 Pro 1TB NVME Gen 4 M.2 SSD
    PSU
    Dell
    Case
    Dell
    Cooling
    Dell
    Keyboard
    Dell KM3322W
    Mouse
    Dell Trackpad or Dell KM3322W
    Internet Speed
    900mb down / 400mb up FTTP
    Browser
    Edge 124.0.2478.67 Beta
    Antivirus
    Windows Defender
    Other Info
    Windows 365
    1TB OneDrive
    Outlook
    Visual Studio Code
    Visual Studio
    Python 3.12.2
    Macrium Reflect
    Dell Update
    MyDell
    Dell SupportAssist
    Dell TB16 Thunderbolt dock
  • Operating System
    Windows 11
    Computer type
    Tablet
    Manufacturer/Model
    Microsoft Surface Pro 7
    CPU
    Core i5 - 1035G4
    Motherboard
    Microsoft
    Memory
    8GB
    Graphics card(s)
    Intel Iris Plus
    Monitor(s) Displays
    Surface touch
    Screen Resolution
    2736 x 1824
    Hard Drives
    128GB
    PSU
    Microsoft
    Case
    Microsoft Keyboard
    Cooling
    None
    Mouse
    Microsoft Arc Intellimouse
    Keyboard
    Microsoft Surface Keyboard
    Internet Speed
    900mb / 400mb FTTP
    Browser
    Edge
    Antivirus
    Windows Defender
Back
Top Bottom