Recent content by Diceman2037

its better than 25h2 on all hardware

read task manager again. slowly.

no

dunno why people are wasting time with uudump for 1575, the x86-64 msu is on the catalog.

its still a first page result. False, you're not accounting for fragmentation - the bane of virtual memory management. Not even the same thing. False: Standby memory is sparse mapped and can be directly ovewriten without consequence, there is no freeing op involved. Windows reports...

26h1 is the fix to 25h2, anything broken in 25h2 is because its a bad backport from it.

Windows 7 and 8 set a 1.5 x phsical minimum, and then grew from there 10 and 11 are 40% of minimum, and you usually crash before the disk has signalled that the pagefile has grown enough to make use of it. not having a pagefile at all is insane.

NativeNVME on Clients @uncyler825 reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 1853569164 /t REG_DWORD /d 1 /f reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Policies\Microsoft\FeatureManagement\Overrides /v 156965516 /t REG_DWORD...

lol, user error. i've had 96week uptimes.

negative, the drivers are in all variants of 26x00, its just lacking a known feature id that is obviously different to the server one. 27965 had it enabled

@uncyler825 any idea what the equivalent ID is on consumer windows? https://techcommunity.microsoft.com/blog/windowsservernewsandbestpractices/announcing-native-nvme-in-windows-server-2025-ushering-in-a-new-era-of-storage-p/4477353

imagine wrongly attributing a widespread cloudflare outage as a windows bug lol. One of your drivers is failing to migrate, look at the log to find out which one.

i was on Release 26200 which had managed to make it to 6899, but then wouldn't go further, DISM deployed 7019 updated a few files in the system folders, but left an inconsistent pending.xml in winsxs, clearing that and reverting with WinRE to beforee 7019 was attempted (1742 was also attempted...

Your chipset or iodie voltages are unstable and the usb controller is being dropped and reset.

PSA This update (and 6901 before it) will not install without the staged leftovers of 26100.1742 If you have removed it with steps from another thread, you will now need to add the kb5043080 msu back with dism. Running the MSU's directly will fail without it, and using DISM to add the 7019...