Insider KB5044388 Windows 11 Insider Dev build 26120.1930 (24H2) - Oct. 4

JGToy · Oct 5, 2024

rseiler said:
I'm curious, is there anyone here with unsupported hardware who was able to install this via WU? After reading a translated comment over on a German forum about this build, I'm beginning to wonder if the reason I only got a 0xc1900101 when attempting WU to get to this build was because of this:

"A simple Windows update to „unsupported hardware“ – as before – is no longer possible! All that remains is the Inplace Upgrade option with Zero Limit Iso"

So, yes, I used an ISO to do it, but that's obviously not practical to do on an ongoing basis.

0xC1900101 is so broad that it doesn't necessarily mean anything in and of itself. There was even a fix for a 0xc1900101 in the last Canary (not that I use Canary), and that likely had nothing to do with unsupported hardware.

So, it's plausible that the 0xc1900101 I got in Dev is just a bug that some are hitting, which is what leads me to ask for more experiences with unsupported hardware and Dev.

I just had this problem with one machine and I had to install it with ISO using server option.

JGToy · Oct 5, 2024

Bree said:
It's slow to install because this is a full feature update, not a simple CU, as rseiler spotted earlier. Seems overkill for a minor build update.

Thanks for the update!
I didn't know about the detail. I though it was some other problem.

fg2001gf11F · Oct 5, 2024

This is in the blog, but from what I have seen, they only fixed one particular case that was happening when HDR was turned on with the NVIDIA RTX adapter.
Is anybody still getting the weird pink multiboot menu with this Build?

Fixed an issue for some Insiders with dual boot devices, where the boot menu (where you select which OS to boot into) wasn’t displaying correctly (the color was wrong, and it might only display in half the available space).

dbartenstein · Oct 5, 2024

rseiler said:
I'm curious, is there anyone here with unsupported hardware who was able to install this via WU? After reading a translated comment over on a German forum about this build, I'm beginning to wonder if the reason I only got a 0xc1900101 when attempting WU to get to this build was because of this:

"A simple Windows update to „unsupported hardware“ – as before – is no longer possible! All that remains is the Inplace Upgrade option with Zero Limit Iso"

So, yes, I used an ISO to do it, but that's obviously not practical to do on an ongoing basis.

0xC1900101 is so broad that it doesn't necessarily mean anything in and of itself. There was even a fix for a 0xc1900101 in the last Canary (not that I use Canary), and that likely had nothing to do with unsupported hardware.

So, it's plausible that the 0xc1900101 I got in Dev is just a bug that some are hitting, which is what leads me to ask for more experiences with unsupported hardware and Dev.

Yes, I installed it on an old Dell 6430 under WU.

Mooly · Oct 5, 2024

So this was a biggie... long time to download, long long time to instal and a long long time to run a cleanup.

All seems OK although I noticed all my custom registry entries for fonts (the Windows Current User WindowsMetrics key) had been reset to default values. Other updates have never touched this. Fortunately I exported the key weeks ago and so it was only a moments job to restore.

Free disk space shot down following all this but after a cleanup I'm around 7Gb up on the deal vs disk space before the update. Although nearly 31GB marked for cleanup I ultimately only saw around 24GB reclaimed.

Wonder how Macrium image size will compare. Next on the list after all this.

OAT · Oct 5, 2024

dbartenstein said:
Yes, I installed it on an old Dell 6430 under WU.

Same here on an Asus X751.

rseiler · Oct 5, 2024

@dbartenstein and @OAT

OK, so this is not as clear as I thought then. What workaround does each of you use for WU? I use v13 of Skip_TPM_Check_on_Dynamic_Update.cmd.

Bree · Oct 5, 2024

rseiler said:
OK, so this is not as clear as I thought then. What workaround does each of you use for WU? I use v13 of Skip_TPM_Check_on_Dynamic_Update.cmd.

I have two unsupported devices running Dev, my Systems Two and Four in My Computers below. I use v13 of that script too. Both fail to upgrade with error 0xc1900101. My supported System Five also runs Dev and has upgraded successfully.

rseiler · Oct 5, 2024

@Bree So either the two I mentioned in my last post are using a different workaround (I'm not aware of any others for WU though) or it maybe depends on in what specific ways the given system is unsupported (there are several criteria). In my case, I have no TPM at all and no Secure Boot and the CPU is only Intel Core 2nd gen, so I hit the trifecta.

Mooly · Oct 5, 2024

Bree said:
It's slow to install because this is a full feature update, not a simple CU, as rseiler spotted earlier. Seems overkill for a minor build update.

I was thinking on this and wondering if it could be for a valid reason. Does an update like this effectively 'reset' everyone running the Dev builds to a known starting point. In my case my altered registry settings were set back to defaults for example.

Could it stop tweaks and problems being carried forward and so let MS get a truer picture of how its all going?

Bree · Oct 5, 2024

Bree said:
I have two unsupported devices running Dev, my Systems Two and Four in My Computers below. I use v13 of that script too. Both fail to upgrade with error 0xc1900101. My supported System Five also runs Dev and has upgraded successfully.

@rseiler I run all my Insider builds as native boot vhdx. As such I could copy the Dev .vhdx from my unsupported System Four to an external SSD, native boot that on my supported System Five to complete the upgrade, then copy it back to my System Two. So far that's the only way I have found to upgrade that unsupported device to the latest Dev build.

dbartenstein · Oct 5, 2024

rseiler said:
@dbartenstein and @OAT

OK, so this is not as clear as I thought then. What workaround does each of you use for WU? I use v13 of Skip_TPM_Check_on_Dynamic_Update.cmd.

I did my original Dev install using Rufus quite a while back and I've never had any issues with a WU update.

cereberus · Oct 5, 2024

Bree said:
@rseiler I run all my Insider builds as native boot vhdx. As such I could copy the Dev .vhdx from my unsupported System Four to an external SSD, native boot that on my supported System Five to complete the upgrade, then copy it back to my System Two. So far that's the only way I have found to upgrade that unsupported device to the latest Dev build.

If your host OS on unsupported pc is Pro, a variant on that would be to mount the vhdx on unsupported pc to a Hyper-V virtual machine with the tpm emulator enabled and upgrade in the vm.

Then close down Hyper-V vm and native boot vhdx thereafter.

You would need to ensure you have an EFI partition in the vhdx file. You can clone host efi partition to unsupported vhdx file (do the clone one the host).

That is what I do on my unsupported Lenovo.

You only need to clone efi once.
It can be after the main C drive.

You may need to boot from a Macrium Reflect iso and use the fix windows boot entry option the first time.

This method is essentially same as yours except using a Hyper-V VM rather than a separate pc.

In fact a few years ago, you could only build upgrade a native boot vhdx on host via a virtual machine but somewhere along the line MS removed the restriction allowing vhdx files to be upgraded on host. I think I was the first to report this on this forum (before the following post).

Finally! Upgrading Windows in native boot VHD just got easier

When the Windows Insider Program was started on October 1st, 2014, I immediately decided to run only Fast Ring (later renamed as Dev Channel) builds. I was not interested in current Windows 10, later Windows 11 builds, I simply wanted to know what is coming up, how the future of Windows looks...

www.elevenforum.com

So I am not really coming up with a new solution but revisiting an old solution.

If your host OS is only Home, create a pro native boot vhdx to run Hyper-V. It does not need the Pro vhdx to be activated.

rseiler · Oct 5, 2024

This awfully similar issue (but not about Windows Update) has been making the rounds in the press this week. I wonder if it's coincidental given what some of us experienced with Dev. Maybe, maybe not.

Microsoft cracks down on Windows 11 upgrades for 'incompatible' PCs, but there's a workaround

The endless cat-and-mouse game between Microsoft and the community of devoted Windows hackers just took another turn.

www.zdnet.com

cereberus · Oct 5, 2024

rseiler said:
This awfully similar issue (but not about Windows Update) has been making the rounds in the press this week. I wonder if it's coincidental given what some of us experienced with Dev. Maybe, maybe not.

Microsoft cracks down on Windows 11 upgrades for 'incompatible' PCs, but there's a workaround

The endless cat-and-mouse game between Microsoft and the community of devoted Windows hackers just took another turn.

www.zdnet.com

IMO, that news article is just typical wanabee journalism regurgitating other older articles.

It does not really say anything new that has not been discussed many times on this forum.

s8018572 · Oct 6, 2024

Damn , my windows store app update or KB5043954 all stuck at installing and wont complete after update to this version

Bree · Oct 6, 2024

fg2001gf11F said:
This is in the blog, but from what I have seen, they only fixed one particular case that was happening when HDR was turned on with the NVIDIA RTX adapter.
Is anybody still getting the weird pink multiboot menu with this Build?

Fixed an issue for some Insiders with dual boot devices, where the boot menu (where you select which OS to boot into) wasn’t displaying correctly (the color was wrong, and it might only display in half the available space).

View attachment 111230

My System Five is still pink/half-size with 26120.1903.

There is a reasonably acceptable workaround, thanks go to cereberus.

cereberus said:
A partial workaround is to run MSCONFIG, select boot tab and check option Base Video and option to Make all boot settings permanent.

This tells the bios to display the graphics screen in a slightly lower resolution (1024x768 on my tablet).

So you get a normal looking screen on bootup albeit it does not fill entire screen but it looks much better than the screen display only using left half.

Bree · Oct 6, 2024

rseiler said:
So, it's plausible that the 0xc1900101 I got in Dev is just a bug that some are hitting, which is what leads me to ask for more experiences with unsupported hardware and Dev.

The clue to why we get this bug, but didn't for the Canary channel's recent feature update, could be in the type of update being downloaded. This Dev update is labelled as (ge_release_upr), in other words it's an update repair version.

A normal full feature update is just called (ge_release).

Option One
Repair Install Windows 11 via Windows Update

This will download and install a repair version of the OS. This operation reinstalls the OS that you have and will not remove any files, settings, or apps.

Repair Install Windows 11 with an In-place Upgrade

This tutorial will show you how to do a repair install of Windows 11 by performing an in-place upgrade without losing anything. If you need to repair or create a new recovery partition or having problems with the Windows 11 operating system on your PC, and the usual solutions will not fix it...

www.elevenforum.com

Gmy77 · Oct 6, 2024

Same as many other... i have no TPM or UEFI etc... i have NO problems AT ALL on ANY PREVIOUS VERSION. This, the 1930 print the same error. Now i find various files fixed using SFC&C. then i RESET Windows update using command line and i re-try... OTHERWISE... I have the feeling that some other method will appear soon..." unless Microsoft wants HAMMER THE FINGER ITSELF... and say "D'OH.

rseiler · Oct 6, 2024

Mooly said:
I was thinking on this and wondering if it could be for a valid reason. Does an update like this effectively 'reset' everyone running the Dev builds to a known starting point. In my case my altered registry settings were set back to defaults for example.

Could it stop tweaks and problems being carried forward and so let MS get a truer picture of how its all going?

Certainly plausible, but it sure would be nice if they would communicate stuff instead of acting all black box-y. But if you're right, maybe we're on the precipice of:

https://twitter.com/x/status/1843015157217390812

Insider KB5044388 Windows 11 Insider Dev build 26120.1930 (24H2) - Oct. 4

Changes and Improvements gradually being rolled out to the Dev Channel with toggle on*​

[General]​

[Fonts]​

[Windows Sandbox]​

Fixes gradually being rolled out to the Dev Channel with toggle on*​

[Other]​

Changes and Improvements gradually being rolled out to everyone in the Dev Channel​

[Settings]​

Known issues​

[General]​

[Start menu]​

New Clock widgets: Countdown and Timer​

Reminders for Windows Insiders in the Dev Channel​

Too young to know

My Computer

Too young to know

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Pragmatic Member

My Computers

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computer

Well-known member

My Computer

Member

My Computer

Well-known member

My Computers

Well-known member

My Computers

|GG|

My Computer

Well-known member

My Computer

Similar threads

Changes and Improvements gradually being rolled out to the Dev Channel with toggle on*

[General]

[Fonts]

[Windows Sandbox]

Fixes gradually being rolled out to the Dev Channel with toggle on*

[Other]

Changes and Improvements gradually being rolled out to everyone in the Dev Channel

[Settings]

Known issues

[General]

[Start menu]

New Clock widgets: Countdown and Timer

Reminders for Windows Insiders in the Dev Channel