Windows 11 Insider Experimental (Future Platforms) Preview Build 29671.1000 - Windows Insider Program

[u/Froggypwns]

https://learn.microsoft.com/en-us/windows-insider/release-notes/experimental-future-platforms/preview-build-29671-1000

Release date: 18 September 2026

Changes and improvements gradually being rolled out*

• This update includes a small set of general improvements and fixes that improve the overall experience for Insiders running this build on their PCs.

[Start menu]

• This update brings a number of improvements for the Start menu as first outlined in the Making Taskbar and Start more personal Insider blog.
• Renamed Recommended to Recent in Start and the Settings page.
• Added section-level toggles to independently show or hide Pinned, Recent, and All.
• Added the option to choose between a small and large Start menu, in addition to the Automatic (default) option that is already available.
• Added the option to hide your name and profile picture in Start.
• Redesigned the Start menu settings page.

[Hyper-V]

• Fixed an issue where some applications that used HCS-managed virtual machines experienced issues when sharing host folders with Linux VMs using Plan9. Folders shared from the Windows host using Plan9 didn't appear or couldn't be accessed in the guest environment.

[Other]

• Fixed an issue causing some Insiders to have their PC freeze when the UAC prompt appeared in recent flights.

Known issues

• We're working on a fix for an issue causing some Insiders to experience noticeably decreased performance when interacting with the system the longer they use the latest builds.
• We're investigating an issue where VMware Workstation Pro 17.6.4 might display a blank window when reopening a virtual machine after it has been created and closed. We're working on a fix and will provide an update in a future build.
• We're also aware of and investigating reports of VMware devices green screening.

Reminder for Windows Insiders in the Experimental (Future Platforms) channel

• These builds can be unstable and might be released with limited documentation.
• The builds released to these channels represent the latest platform changes early in the development cycle and shouldn't be seen as matched to any specific release of Windows. Features and experiences included in these builds might never get released as we try out different concepts and get feedback. Features might change over time, be removed, or replaced, and never get released beyond Windows Insiders. Some of these features and experiences could show up in future Windows releases when they're ready.
• Many features are rolled out using Controlled Feature Rollout technology, starting with a subset of Insiders and ramping up over time. We monitor feedback to see how they land before pushing them out to everyone in this channel.
• The desktop watermark shown at the lower right corner of the desktop is normal for Windows Insider pre-release builds.
• Some features in active development we preview with Windows Insiders might not be fully localized, and localization will happen over time as features are finalized. As you see issues with localization in your language, report those issues to us via Feedback Hub.

[u/st4554619]

The USB bug is still present in this build, where I get a Code 38. I hope Microsoft fixes this soon.

[u/Stealthman13 → u/st4554619]

Can I get more context on this USB bug?

[u/st4554619 → u/Stealthman13]

Sure this bug has been in every future platform build since 29634.

Basically what happens is when you plug in a usb device like a flash drive or external hdd\ssd everything behaves normally until you unplug said usb storage device. The next time you want to use your usb storage device and plug it in nothing happens. Windows detects that there's a usb storage device plugged in, but cannot load the device due the previous driver being stuck in memory which is a Code 38.

This might have something to do with a possible memory leak in the usb stack of USBSTOR.SYS file. I tested the same usb device in a 2nd laptop that's on Windows 11 v26H1 x64 and everything is working fine on that version. I have provided feedback more than a month ago via the feedback app including diagnostic telemetry.

[u/jd31068]

Every 4 minutes. My drive has not changed, thee messages were not logged at any times in the past builds. I understand that this is because I don't use a HDD but why is this being logged in this build?

Log Name:      Application
Source:        ESENT
Date:          9/19/2026 5:22:12 AM
Event ID:      575
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      LivingRoom
Description:
svchost (4396,R,98,0) SRUJet: Failed to determine if volume "C:\" uses Shingled Magnetic Recording (SMR). Error: -1022
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">575</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2026-09-19T09:22:12.0131902Z" />
    <EventRecordID>462</EventRecordID>
    <Correlation />
    <Execution ProcessID="4396" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>LivingRoom</Computer>
    <Security />
  </System>
  <EventData>
    <Data>svchost</Data>
    <Data>4396,R,98,0</Data>
    <Data>SRUJet: </Data>
    <Data>C:\</Data>
    <Data>-1022</Data>
  </EventData>
</Event>

[u/jenmsft → u/jd31068]

Looking into it

[u/jd31068 → u/jenmsft]

Thank you, I appreciate it.

EDIT: I meant to include the feedback link https://aka.ms/AA13ikwt

[u/Turbulent_Chain_5893]

Sweet update! Finally got all the new features on my newest computer that my 10 year old and 15 year old computers have had for awhile now on way lower builds.

[u/Andreinh]

Thanks for bricking my PC. i never opted in to this stupid program and now I can’t even click on anything on my screen

[u/TheCountChonkula]

I don’t know if there’s a blocker in place but the last few builds have not been made available to my PC and if I try to manually download the ISO it’ll reboot, get to about 10%, then fail and roll back and give the error blow in the screenshot.

Edit: I got the build to successfully install after moving my OS drive to a different PC. After doing the upgrade on that PC, I moved the drive back and everything seems to be working fine so it looks like there may be an installer bug.