[DISCUSSION] Windows 11 Build 26100 (PC) [24H2 Retail- GE-release]

.5061 also running for me very smooth

 

As this is 26XXX...Not sure where to go with this one...

Does build beta/preview 26466.ge_current_directbox_flight exist publicly?

This is the build they showed with the new Xbox ROG Ally... would be excited to check it out on another gaming device if it's out there.

 

No problem here with the Kingston A400 SATA SSD (very common model here) 26100.4946
I suspect this problem is on NVMe or M.2

 

I've had no issues currently with transferring large files on 26100.5061.
I've been transferring over 420GB of High Res videos for work (max video size was 86.2GB) between a USB SSD and a couple of NVMe Samsung 9100/990 Pros and drives still functioning as normal.

The only issues I do notice is some random micro freezes when playing videos, plus I have also had to disable hardware/graphics acceleration in browsers so webpages scroll more smoothly and so Netflix videos play correctly.
Unsure if a Nvidia or a Windows issue currently as all stability tests pass 100%

 

You need to login to view this posts content.

 

You don't download 40GB+ UHD 4k linux ISOs

See above.

Sata ssd & hdd models also reported to have faced this issue.

Only write to internal drives matter it seems & usb ssd are limited by the usb interface not to mention samsung ssd seem to be prone to data corruption but not bricking due to this issue so as a pracaution do check hash values of files after being written to internal ssd by comparing to source.

 

My PC (on Release Preview channel) updated last night to 26200.5751. It did a full install for it, not just an enablement package. It's now showing as 25H2.

EDIT: For some reason it's now showing as on the Dev Channel. Interesting. I didn't change it.

 

This is such a pain, updating each game individually and running flush buffer for the volume just to reduce the risk of drive failure
I've turned off write caching aswel on other drives

 

How can Microsoft get away with destroying entire SSDs of data? I mean someone who doesn't follow the tech news about Windows 11 might have their windows auto-update and then the next day the person might copy tons of data from the disk and there's a chance it'll get corrupted and the person can lose data that is worth hundreds or thousands of dollars/euros. We're talking about personal pictures, database files, university projects, etc. This should be illegal!!!

Even LTSC versions are affected!!! Medical devices use those!!!

This is unacceptable. It's been days! Still no fix.

 

there might be a fix, cu just dropped

Nothing for beta though

 

Not strictly true. Phison-based and DRAM-less drives are over-represented in community tests and reports, and many threads single them out; Phison has been named in testing and is investigating. However, multiple reports show other controller families/brands also exhibiting problems, so it’s not an exclusive or proven one-vendor fault.

The reproducible pattern most investigators report is failures occurring after approximately 50 GB of sustained writes, when the drive is already fairly full (≈60% or more).
Some DRAM-less Phison units reportedly fail at lower write volumes in certain cases, but the widely reported trigger is far larger than 7–8 GB.

Mostly NVMe, but not exclusively.
There are also scattered reports of SATA SSDs and even some HDDs showing problems in a few threads. So not been proven to be strictly limited to NVMe, user reports show a small number of non-NVMe devices affected

 

KB5064081?
Am not seeing /getting anything on MUC, neither upon manually checking for updates in Windows.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Code:

Add-Type @"
using System;
using System.Runtime.InteropServices;
using Microsoft.Win32.SafeHandles;

public class FlushVolume {
    [DllImport("kernel32.dll", SetLastError = true)]
    public static extern SafeFileHandle CreateFile(
        string lpFileName,
        uint dwDesiredAccess,
        uint dwShareMode,
        IntPtr lpSecurityAttributes,
        uint dwCreationDisposition,
        uint dwFlagsAndAttributes,
        IntPtr hTemplateFile);

    [DllImport("kernel32.dll", SetLastError = true)]
    public static extern bool FlushFileBuffers(SafeFileHandle hFile);
}
"@

$volume = "\\.\F:"
$handle = [FlushVolume]::CreateFile($volume, 0x40000000, 3, [IntPtr]::Zero, 3, 0, [IntPtr]::Zero)

if ($handle.IsInvalid) {
    Write-Host "❌ Failed to open volume $volume"
} else {
    $result = [FlushVolume]::FlushFileBuffers($handle)
    $handle.Close()

    if ($result) {
        Write-Host "✅ Volume flush successful for $volume"
    } else {
        Write-Host "❌ Volume flush failed for $volume"
    }
}

Buffer flush, only when the drive is idle, dont attempt a flush while you are writing data. Change the drive letter yourself
Maybe turn off enable write caching also ...to lower the risks of drive failure, keep to a minimum file size per write session, nothing above above 50GB

Not recommended for frequent use either

 

This is really unacceptable.
Microsoft is losing even the small credibility it had left, all for chasing this s**tty AI trend and selling user data along with it.

 

Does anyone know if enrolling into the Beta channel from stable does a full install like going from stable to dev? Or does it just install an update like it should with no windows.old folder?