On Sat, Oct 10, 2026 at 02:38:53PM +0800, Qiliang Yuan wrote:
> Hi Wei, Sean,
> 
> Wei, on the v1 thread
> (https://lore.kernel.org/r/[email protected]):
> 
> On Tue, Sep 29, 2026 at 06:42:22PM -0700, Wei Liu wrote:
> > On Tue, Sep 29, 2026 at 08:57:55AM +0800, Qiliang Yuan wrote:
> > > This machine is fully up to date through Windows Update, and the failure
> > > reproduces on this build, so the fix does not seem to have reached the
> > > released builds yet.  Which build or channel (e.g. Insider) carries it?
> > > I am happy to test it.
> >
> > Windows 11 Pro, version 26H1 should have the fix.
> 
> I upgraded and retested.  The failure still reproduces on 26H2:
> 
[...]
> Wei, could you check with your colleague which build actually carries
> the fix?  If it is only in 26H1 and not yet in 26H2, that would explain
> it.  I am happy to test any build.
> 

Sorry for the late reply.

I asked my colleague. There are two options:

1. Go back to 26H1.
2. Stay on 26H2, but wait until December, after the 11.D LCU update is
   delivered (ETA late November).

Wei

Reply via email to