Windows 24H2 compatibility bleurgh!

Maybe by the time Lenovo thinks my mid-2024 ThinkPad is ready to take 24H2 it will be time for MS to roll 25H2…

https://www.theregister.com/2024/12/19/windows_11_24...

😂

My Asus motherboard desktop got 24H2 last Friday so things are moving slowly.

Inspiron, refurbished from Dell, bought in February was updated last week. I generally 'check for updates' every couple of weeks.

In reply to a post by broadband66:

Inspiron, refurbished from Dell, bought in February was updated last week. I generally 'check for updates' every couple of weeks.

I did try applying it a few times on the insider preview program - crashed and rolled itself back each time.

Have checked and still no 24H2 on default update mode, clearly still some hangups with Lenovo drivers / tin.

if you want 24H2 now then do the upgrade online and use the Windows 11 Installation Assistant from here
https://www.microsoft.com/en-us/software-download/wi...
You can choose to keep all your programs and files.

I would suggest you make an image of your drive before you start..

No dice I'm afraid. Tried it again overnight using the Windows 11 Installation Agent via your link. Restarted the machine after download and it went through the update process...got to around 63% before it choked and died.

Its now rolling itself back again to 23H2 (yet again, probably the 4th time).

So yar, still very much bleurgh here on 24H2 I'm afraid!

FWIW - I've opened a support ticket with Lenovo (machine is barely 5 months old) just to see what gives....

Been offering 24H2 to me on Samsung laptop for several weeks now. I intend to defer updating for as long as possible. Don't want/need most of the new stuff anyway.

In reply to a post by Thaumaturge:

Been offering 24H2 to me on Samsung laptop for several weeks now. I intend to defer updating for as long as possible. Don't want/need most of the new stuff anyway.

I'm running it on other devices (virtual machines) and it's been fine. It's a driver / tin issue. In an email reply to my support ticket, Lenovo basically told me to update the BIOS, Video and some other miscellaneous drivers to the latest available version. Some of which were only released on Christmas Eve, but I'd already updated them prior to (the most recent) attempt at 24H2 update last night. It still chokes and eventually rolls itself back to 23H2.

So who knows. Maybe it will be ready to update sometime in 2025...🤣

In reply to a post by Pheasant:

FWIW - I've opened a support ticket with Lenovo (machine is barely 5 months old) just to see what gives....

It was only early Dec before my work 2022 T14 got the right drivers to release the hold, so they’re obviously working on it.

have you tried running sfc /scannow and
DISM.exe /Online /Cleanup-image /Scanhealth && DISM.exe /Online /Cleanup-image /Restorehealth
from admin command prompt?
They may just fix an unseen error that prevents you from upgrading.

Me or JC? (I know you replied to JC, but I’m hazarding your comment was for moi?)

Anyhow I’ve got bigger problems now - Lenovo Support “solution” to send me a link to create a recovery key and reimage the machine from scratch.

Anyway. This was the result of that little 3 hour endeavour.

https://postimg.cc/w74K6Rd5

Machine won’t clean boot at all now. So something to fix tomorrow. At least I know what the dirty culprit is 😂. Did I mention how much I love Windows. Not 😄

Yikes. We just reset on device at a corporate level if changing user.

I am happily playing on Solus Plasma (Linux) and haven't booted (dual) into Win 11 in weeks. Only downside to Solus in a rolling distro is updates every week but so far the developers haven't introduced any bugs or snafus in my 6 months of using it.

Updates every week are a plus, not a downside.

I’m all set for Windows alternatives. Need a working Windows 11 laptop. Ideally 24H2. Hence thread

In reply to a post by jchamier:

Yikes. We just reset on device at a corporate level if changing user.

Yup. Something is horribly amiss (that's me being polite at 7:20-ish am), if a new machine BSOD's after a re-image from the official recovery media 🤣

Mmm. Difficult to generalise - depends what all the updates are for. I tend to be more a subscriber to the "if it ain't broke don't fix it" school of thought.

I subscribe to the "always apply security patches" school of thought. I'd be surprised if a week goes by without any.

Just because I think it ain't broke doesn't mean that someone else doesn't know better.

In reply to a post by TinyMongomery:

I subscribe to the "always apply security patches" school of thought. I'd be surprised if a week goes by without any.

Always the case in enterprise systems, with commercially supported Linux distros such as RHEL you want to know the exact built state, not cherry pick packages. Or your third party enterprise software won’t be supported on the server. Just not worth the headaches.

Just because I think it ain't broke doesn't mean that someone else doesn't know better.

This was why MS went to the one big patch per month, unlike the NT4, and XP days.

In reply to a post by Pheasant:

I’m all set for Windows alternatives. Need a working Windows 11 laptop. Ideally 24H2. Hence thread

Hopefully the Lenovo media is restoring 23H2 as it appears the Oct & Nov patches if added to the 24H2 removable media when building cause a problem. The Dec patch resolves. Won’t affect many people whom don’t build machines from removable media. My employer is still in pilot for 24H2, only those whom have opted in to be on the troubled path have got it. And those of us whom have to support customer systems 🤨

https://www.theregister.com/2024/12/27/microsoft_win...

Cheers. It’s a topic for discussion with Lenovo Support. From what I can tell it’s using image version 10.0.26100.1

In reply to a post by Pheasant:

Cheers. It’s a topic for discussion with Lenovo Support. From what I can tell it’s using image version 10.0.26100.1

I think that build number is 24H2, assuming its the Windows build number.

https://learn.microsoft.com/en-us/windows/release-he...

Or

https://betawiki.net/wiki/Windows_11_build_26100.1

Yeah. From what I could find it’s an early foundation build of 24H2. It’s in Lenovo’s court right now to give me a workable solution.

A recovery key build that then BDODs is pretty [censored].

In reply to a post by Pheasant:

Yeah. From what I could find it’s an early foundation build of 24H2. It’s in Lenovo’s court right now to give me a workable solution. A recovery key build that then BDODs is pretty [censored].

Sounds like they’ve released an untested version! Is there not an older one on the website to download as well? Shame; they used to be better

That’s what I need to find out during business hours. As far as I can tell the image is based on a lookup of the serial number of the machine. It delivers precisely one configured build of W11. Which makes sense, given the variety of factory configurations and add-in options available for these machines.

I agree it’s a real let-down by Lenovo especially on brand-new tin. They’re better than this (or used to be).

Verbatim Lenovo instructions below, following my first contact:

There was also a PDF attachment, summarising the process for creating and downloading a USB recovery key.

————////————

Thank you for contacting Lenovo Technical Support,

We are contacting you regarding the above case you logged with us.

Please update the following drivers from the links bellow:

BIOS/UEFI Update
https://pcsupport.lenovo.com/gb/en/products/laptops-...

Chipset Driver Update (Motherboard Devices)
https://pcsupport.lenovo.com/gb/en/products/laptops-...

The Graphics Driver
https://pcsupport.lenovo.com/gb/en/products/laptops-...


If the issue still persist try to re-image the laptop using the Lenovo recovery media as instructed bellow:

1. Use the following link to create a Lenovo account with a valid email address:
https://pcsupport.lenovo.com/gb/en
2. Enter the serial number of the device to request a recovery OS:
https://pcsupport.lenovo.com/gb/en/lenovorecovery?li...

Instructions to create the recovery key:
https://support.lenovo.com/gb/en/solutions/ht103653


https://www.youtube.com/watch?v=xXC8GYm8l34

Once the reinstallation is done check for pending driver updates using the Lenovo Vantage or System update application. The link to download the application:
https://support.lenovo.com/gb/en/downloads/ds012808

After completing all of the above, please advise us, and provide us with information was the reported issue resolved and still remains?

Kind Regards,

Customer Support Representative, Lenovo PC Front Office
IBM TSS CIC Sofia, IBM Systems
_______________________________________________________
Phone: Phone: UK 03337773991, option 3 | Phone: IE 01 68 62 650, option 3
E-mail: [email protected]

Get-out-of-jail card: download and create a vanilla bootable copy of Win 11 24H2 and piecemeal add back in all the individual Lenovo and third-party system drivers until find the one that borks Windows.

(Based on the BsOD I think it’s the Intel WiFI adapter driver that’s bricking it)

This is not what I’d expect expect to have to do on a new fully configured / imaged machine and likely will be rhe best part of 3 to 4 hours which quite frankly is a pretty rubbish….

Does it start in safe mode? If so you could disable all suspect devices and enable them one by one to determine the culprit.

Doesn't get that far I'm afraid.

In my Windows Insider capacity I think I saw a report that safe mode is broken on 24H2 but it escapes me which build so that may not help unless it has been fixed recently.

In reply to a post by Banger:

In my Windows Insider capacity I think I saw a report that safe mode is broken on 24H2 but it escapes me which build so that may not help unless it has been fixed recently.

Broke on some beta builds but nothing that is released. Insider being a test platform that is expected.

In reply to a post by Pheasant:

(Based on the BsOD I think it’s the Intel WiFI adapter driver that’s bricking it)

My T14 was held back from 24H2 by Intel graphics driver until that was updated to Lenovo’s modified one.

This is not what I’d expect expect to have to do on a new fully configured / imaged machine and likely will be rhe best part of 3 to 4 hours which quite frankly is a pretty rubbish….

Its mad, Lenovo should be able to provide you a recovery for 23H2 …!!

Spent an hour and half, with a very nice chap from Lenovo Support checking various diagnostics on the machine and then running through the install process again from the Lenovo recovery media.

After a very long time on the call, with the machine not yet done, we said we'd reconvene to take a break and let the laptop finish up....

Just returned to laptop now to find that at the end of it all - yep you guessed it's rebooted itself one final time and right back into the exact same BSOD error.

Now waiting for my call back from them....

In reply to a post by Pheasant:

Now waiting for my call back from them....

I guess 3rd line have issued an updated USB and not tested it enough, which is causing 1st and likely 2nd line to internally go "?!?!?".... I also suspect a lot of the people they would ask are on holiday/vacation, especially if the experts are still in Raleigh, NC, USA.

Edited by jchamier (Mon 30-Dec-24 16:12:37)

Full update tomorrow, but I’m glad to say we’ve found the culprit….and it was my OWC Thunderbolt 3 Pro dock!!

I never would’ve given it a second thought, given it was working for years with all sorts of machines and most recently with the very same Thinkpad but running 23H2 - moving to a 24H2 update or 24H2 base build causes an immediate BSOD.

In reply to a post by Pheasant:

Full update tomorrow, but I’m glad to say we’ve found the culprit….and it was my OWC Thunderbolt 3 Pro dock!!

D'Oh!

🙈 yes muppetry at its finest!!

Do you know when you do something, without further pause for thought; so all along whilst re-imaging this thing I thought, pah it's just a power supply. Doesnt even need any drivers. Didn't even cross my mind. It wasn't until I was on the phone for the second lengthy spell with 'Bobby' (from IBM Bulgaria - yes they provide support to Lenovo), and he was chatting with his own 2/3rd line team that we realised. Do'h!!!

Flipped the laptop over, held in the teeny recessed button (only a bent staple would fit) you really need to know this thing is there. Held that sucker down for a minimum of 30 seconds, turned it back over. Power it back up using the original plain USB-C plug pack power supply and rebooted for the umpteenth time. This time it survived that last reboot and on through the recovery.

Clearly there is something driver not likey likey, lurking dark and deep within W11 24H2, that absolutely was not there ever before, even as recently with 23H2 or any previous W10 etc version, that suddenly and instantly triggers a BSOD meltdown.

In reply to a post by Pheasant:

Do you know when you do something, without further pause for thought; so all along whilst re-imaging this thing I thought, pah it's just a power supply. Doesnt even need any drivers. Didn't even cross my mind. It wasn't until I was on the phone for the second lengthy spell with 'Bobby' (from IBM Bulgaria - yes they provide support to Lenovo), and he was chatting with his own 2/3rd line team that we realised. Do'h!!!

I think the bit of IBM that provides support to Lenovo is the bit left after they sold nearly 100,000 people as the new company Kyndryl.

Flipped the laptop over, held in the teeny recessed button (only a bent staple would fit) you really need to know this thing is there. Held that sucker down for a minimum of 30 seconds, turned it back over. Power it back up using the original plain USB-C plug pack power supply and rebooted for the umpteenth time. This time it survived that last reboot and on through the recovery.

I've seen those buttons, temporarily disconnect teh battery so you get a proper power down. Like yanking the mains cable out of a desktop.

Clearly there is something driver not likey likey, lurking dark and deep within W11 24H2, that absolutely was not there ever before, even as recently with 23H2 or any previous W10 etc version, that suddenly and instantly triggers a BSOD meltdown.

Thunderbolt is a complex protocol, maybe it will work when the 24H2 is installed and fully patched? I've got a Lenovo TB3 dock I use with the work T14, and it works okay with a personal MSSurface Pro.

In reply to a post by jchamier:

Clearly there is something driver not likey likey, lurking dark and deep within W11 24H2, that absolutely was not there ever before, even as recently with 23H2 or any previous W10 etc version, that suddenly and instantly triggers a BSOD meltdown.

Thunderbolt is a complex protocol, maybe it will work when the 24H2 is installed and fully patched? I've got a Lenovo TB3 dock I use with the work T14, and it works okay with a personal MSSurface Pro.

Fully patched it all. Rebooted it. Disconnected it from the USB-C charger. Connected it back to the dock and...bam instant BSOD.

Think OWC have now retired/deprecated this particular dock model; Thunderbolt 3 Pro Dock. The Windows Ethernet drivers available from that link are Marvell AQtion v2.2.3.0 for Windows 10 from February 2021.

The new replacement model they introduced this year Thunderbolt Pro Dock however points to exactly the same drivers! Weird.

However I know that Marvel have on their public website much newer 10GbE network drivers -> Marvell AQtion V3.1.10 (23 April 2024). There also looks like there is an adapter firmware updater available from Marvell...

My plan is to try that all, and approach OWC Support in the new year with my 24H2 discovery!

Think I'll definitely give this new Marvell AQtion V3.1.10 driver a try.

Looks like it passed WHQL on 11 August 2024 - so it should be solid for both the old and new OWC Thunderbolt Pro docks

In reply to a post by Pheasant:

Think I'll definitely give this new Marvell AQtion V3.1.10 driver a try.

I guess its worth a try, but I’d be surprised if an Ethernet driver makes a difference. As there are a serious number of ports on that dock, I wonder if something else is triggering the BSOD, perhaps the eSATA as I’ve not seen that for years.

Good point - I'll disconnect everything and reconnect one by one...

Think I'll take a closer look at this particular dock too. Just recalled that I had noticed some time ago, that it was flapping on the ethernet switch logs. Never the best of signs really.

I have a couple of identical docks here (in our home office and for the kids laptops) and they are fine. Possibly the easiest thing would be to connect to one and see if it BSODs there.

A process of elimination for the next few days.

Edited by Pheasant (Tue 31-Dec-24 19:12:05)

The new v3 Marvell driver is in play - works fine with the plain OWC dock now - I’ve tested two docks just to make sure it wasn’t a hardware fault with one dock. All good. Sort off….

As soon as I reconnect Dell monitor via Thunderbolt into dock…near instant BSOD!

This Dell UltraSharp monitor (with its own dock, Thunderbolt, USB and Gig Ethernet port!) has worked flawlessly with all manner of machines plugged into the OWC dock and correspondingly with it….Including this Thinkpad in it original 23H2 Windows11 build!! So will have a closer look at the windows system logs to see what is going on with 24H2 and this BSOD.

TBC!

OK now getting somewhere. Machine will BSOD when Dell UltraSharp U4021QW monitor is connected via Thunderbolt ports, via OWC dock:

This is the same BSOD error when previously attempting an in-line upgrade from 23H2 to 24H2 or doing a clean install of 24H2 from the Lenovo Recovery media for this machine.

WinDbg debug output, following analysis as follows:

*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: ffff9581fd9db008, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff80648f654a6, address which referenced memory

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 1484

Key : Analysis.Elapsed.mSec
Value: 4878

Key : Analysis.IO.Other.Mb
Value: 1

Key : Analysis.IO.Read.Mb
Value: 1

Key : Analysis.IO.Write.Mb
Value: 23

Key : Analysis.Init.CPU.mSec
Value: 609

Key : Analysis.Init.Elapsed.mSec
Value: 94284

Key : Analysis.Memory.CommitPeak.Mb
Value: 89

Key : Analysis.Version.DbgEng
Value: 10.0.27725.1000

Key : Analysis.Version.Description
Value: 10.2408.27.01 amd64fre

Key : Analysis.Version.Ext
Value: 1.2408.27.1

Key : Bugcheck.Code.LegacyAPI
Value: 0xd1

Key : Bugcheck.Code.TargetModel
Value: 0xd1

Key : Dump.Attributes.AsUlong
Value: 21808

Key : Dump.Attributes.DiagDataWrittenToHeader
Value: 1

Key : Dump.Attributes.ErrorCode
Value: 0

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1

Key : Dump.Attributes.LastLine
Value: Dump completed successfully.

Key : Dump.Attributes.ProgressPercentage
Value: 0

Key : Failure.Bucket
Value: AV_WiManHio!unknown_function

Key : Failure.Hash
Value: {ba8258fc-371d-0c3a-2d7a-10fe19f59a3e}

Key : Hypervisor.Enlightenments.ValueHex
Value: 7417df84

Key : Hypervisor.Flags.AnyHypervisorPresent
Value: 1

Key : Hypervisor.Flags.ApicEnlightened
Value: 0

Key : Hypervisor.Flags.ApicVirtualizationAvailable
Value: 1

Key : Hypervisor.Flags.AsyncMemoryHint
Value: 0

Key : Hypervisor.Flags.CoreSchedulerRequested
Value: 0

Key : Hypervisor.Flags.CpuManager
Value: 1

Key : Hypervisor.Flags.DeprecateAutoEoi
Value: 1

Key : Hypervisor.Flags.DynamicCpuDisabled
Value: 1

Key : Hypervisor.Flags.Epf
Value: 0

Key : Hypervisor.Flags.ExtendedProcessorMasks
Value: 1

Key : Hypervisor.Flags.HardwareMbecAvailable
Value: 1

Key : Hypervisor.Flags.MaxBankNumber
Value: 0

Key : Hypervisor.Flags.MemoryZeroingControl
Value: 1

Key : Hypervisor.Flags.NoExtendedRangeFlush
Value: 0

Key : Hypervisor.Flags.NoNonArchCoreSharing
Value: 1

Key : Hypervisor.Flags.Phase0InitDone
Value: 1

Key : Hypervisor.Flags.PowerSchedulerQos
Value: 0

Key : Hypervisor.Flags.RootScheduler
Value: 0

Key : Hypervisor.Flags.SynicAvailable
Value: 1

Key : Hypervisor.Flags.UseQpcBias
Value: 0

Key : Hypervisor.Flags.Value
Value: 55447806

Key : Hypervisor.Flags.ValueHex
Value: 34e10fe

Key : Hypervisor.Flags.VpAssistPage
Value: 1

Key : Hypervisor.Flags.VsmAvailable
Value: 1

Key : Hypervisor.RootFlags.AccessStats
Value: 1

Key : Hypervisor.RootFlags.CrashdumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.CreateVirtualProcessor
Value: 1

Key : Hypervisor.RootFlags.DisableHyperthreading
Value: 0

Key : Hypervisor.RootFlags.HostTimelineSync
Value: 1

Key : Hypervisor.RootFlags.HypervisorDebuggingEnabled
Value: 0

Key : Hypervisor.RootFlags.IsHyperV
Value: 1

Key : Hypervisor.RootFlags.LivedumpEnlightened
Value: 1

Key : Hypervisor.RootFlags.MapDeviceInterrupt
Value: 1

Key : Hypervisor.RootFlags.MceEnlightened
Value: 1

Key : Hypervisor.RootFlags.Nested
Value: 0

Key : Hypervisor.RootFlags.StartLogicalProcessor
Value: 1

Key : Hypervisor.RootFlags.Value
Value: 1015

Key : Hypervisor.RootFlags.ValueHex
Value: 3f7


BUGCHECK_CODE: d1

BUGCHECK_P1: ffff9581fd9db008

BUGCHECK_P2: 2

BUGCHECK_P3: 0

BUGCHECK_P4: fffff80648f654a6

FILE_IN_CAB: 010825-22218-01.dmp

TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b


DUMP_FILE_ATTRIBUTES: 0x21808
Kernel Generated Triage Dump

FAULTING_THREAD: ffffe1890f6c4040

READ_ADDRESS: fffff806b57c34b0: Unable to get MiVisibleState
Unable to get NonPagedPoolStart
Unable to get NonPagedPoolEnd
Unable to get PagedPoolStart
Unable to get PagedPoolEnd
unable to get nt!MmSpecialPagesInUse
ffff9581fd9db008

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

TRAP_FRAME: ffffdd8c6858f760 -- (.trap 0xffffdd8c6858f760)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffdd8c6858f9a8 rbx=0000000000000000 rcx=ffffdd8c6858f9a8
rdx=ffff9581fd9db008 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80648f654a6 rsp=ffffdd8c6858f8f8 rbp=0000000000000000
r8=000000000000001c r9=000000000000001c r10=1fffff00c91e9668
r11=004b014c402e0073 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po cy
WiManHio+0x254a6:
fffff806`48f654a6 0f1002 movups xmm0,xmmword ptr [rdx] ds:ffff9581`fd9db008=????????????????????????????????
Resetting default scope

STACK_TEXT:
ffffdd8c`6858f618 fffff806`b4e8dce9 : 00000000`0000000a ffff9581`fd9db008 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
ffffdd8c`6858f620 fffff806`b4e88fa8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiBugCheckDispatch+0x69
ffffdd8c`6858f760 fffff806`48f654a6 : fffff806`48f64e93 00000000`00000000 ffffe189`0f6c1310 ffffdd8c`6858faa0 : nt!KiPageFault+0x468
ffffdd8c`6858f8f8 fffff806`48f64e93 : 00000000`00000000 ffffe189`0f6c1310 ffffdd8c`6858faa0 00000000`00000000 : WiManHio+0x254a6
ffffdd8c`6858f900 00000000`00000000 : ffffe189`0f6c1310 ffffdd8c`6858faa0 00000000`00000000 00000000`00000000 : WiManHio+0x24e93


SYMBOL_NAME: WiManHio+254a6

MODULE_NAME: WiManHio

IMAGE_NAME: WiManHio.sys

STACK_COMMAND: .process /r /p 0xffffe189044d8040; .thread 0xffffe1890f6c4040 ; kb

BUCKET_ID_FUNC_OFFSET: 254a6

FAILURE_BUCKET_ID: AV_WiManHio!unknown_function

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {ba8258fc-371d-0c3a-2d7a-10fe19f59a3e}

Followup: MachineOwner
---------

Further update following testing. A direct Thunderbolt connection between the laptop and monitor is fine. Can actually use the (Realtek chipped) gigabit Ethernet port on the monitor too.

However then connecting the monitor back to the OWC dock as it was originally, will induce an instant BSOD.

So to recap:
- OWC dock on its own is fine, in-built 10GbE connection is working fine
- Dell monitor on its own is fine, in-built GbE connection is working fine

- OWC dock + Dell monitor = BSOD with 24H2 (however used to work fine on Win 11 23H2)

I just had a scary moment with 24H2, I was finally offered the update this morning and started the update but after it rebooted and started the update it sat there for a good 20 minutes with just a black screen and a mouse cursor and no hard disk activity. I started to worry and was close to doing a hard reboot but for one reason or another decided to connect up one of the spare HDMI ports in addition to the normal DP port I use and the DP port then come to life and the disk light started flashing and the update continued on to a successful completion. All very strange that the update hung until one of the HDMI ports was connected up.