New Windows 10 Insider Preview Fast Build 18312 (19H1) - Jan. 9 Insider

Fisher Mann · 09 Jan 2019

Downloaded and restarted while cooking and eating supper. Seems all went fine thankfully.

martyfelker · 09 Jan 2019

Record size for previous windows build (windows.old basically) Now to linux and sanity!

New Windows 10 Insider Preview Fast Build 18312 (19H1) - Jan. 9-disk-cleanup.png

JGToy · 09 Jan 2019

All done here, no hiccups!
It took 38 minutes (8 minutes longer than its predecessor).

martyfelker · 09 Jan 2019

Same restart problem in Windows for Workstations VM

New Windows 10 Insider Preview Fast Build 18312 (19H1) - Jan. 9-windows-10-workstations-2019-01-09-19-45-11.png

martyfelker · 09 Jan 2019

Ran Disk Cleanup (System files) and restarted from Start Menu (Update and Restart). This is working!

bordi · 09 Jan 2019

A record 24 minutes from start to finish for me

magilla · 09 Jan 2019

scoopjeff said:

Needed two install attempts at this one, first one refused to restart at first, eventually did and installed to 90% then GSOD. Second attempt worked however simple fixes like X-Fi drivers and IE11 menu bar sadly still not sorted

Oh for God sake - they don’t give anything about people like us who use internet explorer I think —- attempt to get everyone to use that worthless Edge.

smactilactus · 09 Jan 2019

This has got to be some kind of a record for me. This was the fastest new build from clicking on Download, to back on desktop. Less than twenty minutes! It happened so fast, I thought something went wrong. And, my sound has stopped popping and crackling as it was in the last build. Everything EXCEPT Sandbox is working perfectly well. Sandbox crashed my system. So I won't be clicking on that again...

magilla · 09 Jan 2019

f14tomcat said:

I went out of settings and clicked the little taskbar icon saying restart needed, then the restart button worked. That was on skippy. On Fast Ring, I had a notice in Action Center, I clicked restart there, and it went. Sooooo.... some tickle to Restart Button does work, whichever you find.

One computer finished and gave me error message everyone is getting. Went to start button, clicked on update and restart and it completed. A second computer gave me same grief, went to start button and pressed update and restart, returned me to 18309. A third computer crashed in middle of downloading, so started it over. A fourth computer is downloading. So there you have an array of peculiarities. Too bad you can’t get a smooth start with new builds. Tends to ‘color’ your view of the build from the get-go.

Brink · 09 Jan 2019

Update:

New "Known Issues" below added for build 18312.

[ADDED] We’re investigating issues with Windows Sandbox not loading on PCs with multiple GPUs.
[ADDED] In some cases, launching Centennial apps will cause a bindflt.sys bugcheck (GSOD).