Insider Windows 11 Insider Experimental (Future Platforms) build 29599.1000 - May 29



 Windows Insider Blog:

As a reminder, these release notes apply to those who are in the Canary 29500 Series Channel. As we begin the transition to the updated Windows Insider Program, all new build release notes will be labeled under the new channel names, even though Insiders in the Canary 29500 Series Channel may not yet find themselves having transitioned to Experimental (Future Platforms). See the Windows Insider Blog for more details.


Changes and improvements gradually being rolled out

  • This update includes platform changes in moving to a new active development build.
  • Fixed an issue which was causing some Insiders to unexpectedly see an erroneous message saying they weren’t connected to internet (when they actually were) when signing into their Microsoft account in certain apps recently.
  • This update improves CPU speed display on the Performance page of Task Manager for VMs, so it doesn’t show higher than unexpected numbers after resuming from hibernate.

Known issues

  • We have identified an issue internally causing crashes on AMD machines supporting System Guard, meaning these devices in WIP will not be offered this week's Experimental (Future Platforms) build.

Reminder for Windows Insiders in the Canary 29500 Series Channel (soon transitioning to Experimental (Future Platforms))

  • These builds can be unstable and may be released with limited documentation.
  • The builds we release to the Canary 29500 Series Channel represent the latest platform changes early in the development cycle and should not 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 are ready.
  • Many features in the Canary 29500 Series Channel are rolled out using Controlled Feature Rollout technology, starting with a subset of Insiders and ramping up over time as 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.
  • For Windows Insiders who want to be the first to get features gradually rolled out to you, you can turn on the toggle to get the latest updates as they are available via Settings > Windows Update. Over time, we will increase the rollouts of features to everyone with the toggle turned on. Should you keep this toggle off, new features will gradually be rolled out to your PC over time once they are ready.
  • 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, please report those issues to us via Feedback Hub.


 Source:



Check Windows Updates


ISO from Microsoft:



UUP Dump:

64-bit ISO download:

ARM64 ISO download:

 
Last edited:
My install of this latest build doesn't show Experimental either but does say since I have a local account (attached).

View attachment 173184
I also have a Local account for windows, but I have a MS account for insider.
Still shows Canary channel, not yet Experimental (Future Platforms). I think Microsoft has not changed it yet for all insider users, it is a gradual change.
With the same settings, I have Experimental on build 26300.8553 (25H2), but not yet Experimental on this 29599.1000.
We'll see what happens with next updates. 😵‍💫🤷‍♂️

1780379074998.webp
 

My Computer

System One

  • OS
    Windows 11 Pro 25H2
    Computer type
    PC/Desktop
    Manufacturer/Model
    Dell XPS 8930
    CPU
    Intel I9-9900K
    Memory
    64GB
    Graphics Card(s)
    NVIDIA RTX 2060
    Sound Card
    NVIDIA High Definition Audio
    Monitor(s) Displays
    4k Samsung
    Screen Resolution
    3840 x 2160
    Hard Drives
    512GB NVMe, ADATA SU 800, 2TB HDD
For anyone facing a GSOD issue, here is a workaround: someone on the MS feedback hub got a dump and shared the windmp analysis:

***

Code:
SYMBOL_NAME:  NETIO!FeNblTrackAcquireRef+52

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

STACK_COMMAND: .process /r /p 0xffffda0679716040; .thread /r /p 0xffffda068f291540 ; kb

BUCKET_ID_FUNC_OFFSET:  52

FAILURE_BUCKET_ID:  0x139_e_INVALID_REFERENCE_COUNT_NETIO!FeNblTrackAcquireRef

OS_VERSION:  10.0.29599.1000

BUILDLAB_STR:  rs_prerelease

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {28bb9efb-c472-ec58-98ab-a910faa425e3}

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

1: kd> kc
 # Call Site
00 nt!KeBugCheckEx
01 nt!KiBugCheckDispatch
02 nt!KiFastFailDispatch
03 nt!KiRaiseSecurityCheckFailureDispatchTrap
04 NETIO!FeNblTrackAcquireRef
05 fwpkclnt!FwpsAllocateCloneNetBufferList0
[B]06 tunnel!TeredoWfpInitializeCloneForInjection
07 tunnel!TunnelTeredoOffloadSendNbl[/B]
08 tunnel!TunnelUserSendNetBufferList
09 tunnel!TunnelMiniportSendNetBufferLists
0a ndis!ndisMSendNBLToMiniportInternal
0b ndis!NdisSendNetBufferLists
0c tcpip!FlpNdisSendNbls
0d tcpip!FlpSendPacketsHelper
0e tcpip!FlSendPackets
0f tcpip!IppFragmentPackets
10 tcpip!IppDispatchSendPacketHelper
11 tcpip!IppPacketizeDatagrams
12 tcpip!IppSendDatagramsCommon
13 tcpip!IpNlpSendDatagrams
14 tcpip!IppSlowSendDatagrams
15 tcpip!IpNlpFastSendDatagram
16 tcpip!InetFastSendDatagramsOnPathAf
17 tcpip!TcpTcbHeaderSend
18 tcpip!TcpFlushDelay
19 tcpip!TcpReceive
1a tcpip!TcpNlClientReceiveDatagrams
1b tcpip!IppDeliverListToProtocol
1c tcpip!IppProcessDeliverList
1d tcpip!IppReceiveHeaderBatch
1e tcpip!IppReceivePackets
1f tcpip!FlpReceiveNonPreValidatedNetBufferListChain
20 tcpip!FlReceiveNetBufferListChainCalloutRoutine
21 nt!KeExpandKernelStackAndCalloutInternal
22 nt!KeExpandKernelStackAndCalloutEx
23 tcpip!NetioExpandKernelStackAndCallout
24 tcpip!FlReceiveNetBufferListChain
25 ndis!ndisMIndicateNetBufferListsToOpen
26 ndis!ndisMTopReceiveNetBufferLists
27 ndis!NdisMIndicateReceiveNetBufferLists
[B]28 tunnel!TeredoWfpIndicationWorker[/B]
29 tunnel!LwWorker
2a nt!IopProcessWorkItem
2b nt!ExpWorkerThread
2c nt!PspSystemThreadStartup
2d nt!KiStartSystemThread

So the culprit is the Teredo protocol(I leave the task of google what it is to you), and it is run with the IP Helper service, so the workaround is simple: running the command netsh interface teredo set disabledin admin CMD in safe mode, and disable the IP Helper service, but some applications like Xbox multiplayer, enterprise apps, or VPN depend on the IP Helper service, so you still have to revert if you need to use them
 

My Computer

System One

  • OS
    Windows 11, Ubuntu on WSL
    Computer type
    Laptop
    Manufacturer/Model
    HP Envy x360
For anyone facing a GSOD issue, here is a workaround: someone on the MS feedback hub got a dump and shared the windmp analysis:

***

Code:
SYMBOL_NAME:  NETIO!FeNblTrackAcquireRef+52

MODULE_NAME: NETIO

IMAGE_NAME:  NETIO.SYS

STACK_COMMAND: .process /r /p 0xffffda0679716040; .thread /r /p 0xffffda068f291540 ; kb

BUCKET_ID_FUNC_OFFSET:  52

FAILURE_BUCKET_ID:  0x139_e_INVALID_REFERENCE_COUNT_NETIO!FeNblTrackAcquireRef

OS_VERSION:  10.0.29599.1000

BUILDLAB_STR:  rs_prerelease

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {28bb9efb-c472-ec58-98ab-a910faa425e3}

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

1: kd> kc
 # Call Site
00 nt!KeBugCheckEx
01 nt!KiBugCheckDispatch
02 nt!KiFastFailDispatch
03 nt!KiRaiseSecurityCheckFailureDispatchTrap
04 NETIO!FeNblTrackAcquireRef
05 fwpkclnt!FwpsAllocateCloneNetBufferList0
[B]06 tunnel!TeredoWfpInitializeCloneForInjection
07 tunnel!TunnelTeredoOffloadSendNbl[/B]
08 tunnel!TunnelUserSendNetBufferList
09 tunnel!TunnelMiniportSendNetBufferLists
0a ndis!ndisMSendNBLToMiniportInternal
0b ndis!NdisSendNetBufferLists
0c tcpip!FlpNdisSendNbls
0d tcpip!FlpSendPacketsHelper
0e tcpip!FlSendPackets
0f tcpip!IppFragmentPackets
10 tcpip!IppDispatchSendPacketHelper
11 tcpip!IppPacketizeDatagrams
12 tcpip!IppSendDatagramsCommon
13 tcpip!IpNlpSendDatagrams
14 tcpip!IppSlowSendDatagrams
15 tcpip!IpNlpFastSendDatagram
16 tcpip!InetFastSendDatagramsOnPathAf
17 tcpip!TcpTcbHeaderSend
18 tcpip!TcpFlushDelay
19 tcpip!TcpReceive
1a tcpip!TcpNlClientReceiveDatagrams
1b tcpip!IppDeliverListToProtocol
1c tcpip!IppProcessDeliverList
1d tcpip!IppReceiveHeaderBatch
1e tcpip!IppReceivePackets
1f tcpip!FlpReceiveNonPreValidatedNetBufferListChain
20 tcpip!FlReceiveNetBufferListChainCalloutRoutine
21 nt!KeExpandKernelStackAndCalloutInternal
22 nt!KeExpandKernelStackAndCalloutEx
23 tcpip!NetioExpandKernelStackAndCallout
24 tcpip!FlReceiveNetBufferListChain
25 ndis!ndisMIndicateNetBufferListsToOpen
26 ndis!ndisMTopReceiveNetBufferLists
27 ndis!NdisMIndicateReceiveNetBufferLists
[B]28 tunnel!TeredoWfpIndicationWorker[/B]
29 tunnel!LwWorker
2a nt!IopProcessWorkItem
2b nt!ExpWorkerThread
2c nt!PspSystemThreadStartup
2d nt!KiStartSystemThread

So the culprit is the Teredo protocol(I leave the task of google what it is to you), and it is run with the IP Helper service, so the workaround is simple: running the command netsh interface teredo set disabledin admin CMD in safe mode, and disable the IP Helper service, but some applications like Xbox multiplayer, enterprise apps, or VPN depend on the IP Helper service, so you still have to revert if you need to use them
thnx for the fix, but I better wait for them to fix it on the next realease, I use ip6 on my network and Internet provider GNAT, so ot is not an option to disable teredo, you really shouldnt need to disable network protocols for windows to work
 

My Computer

System One

  • OS
    windows 11 pro
    Computer type
    Laptop
    Manufacturer/Model
    msi
    CPU
    i7-10750H
    Motherboard
    MS-17E7
    Memory
    64GB
    Graphics Card(s)
    RTX 2070 + Intel UHD
    Screen Resolution
    1920*1080
    Internet Speed
    1000MB/1000MB Izzi
    Browser
    Brave
    Antivirus
    Avast
Back
Top Bottom