Windows 10 Insider Preview Fast Build 19546.1000 - January 16

f14tomcat · 16 Jan 2020

Wannagofast said:

Update from 18363.592 to 19546.1000 done and dusted using ISO from UUPDump.
New Nvidia driver 450.12 installed. Other than that, I see nothing unusual to report.

peace
wanna

You took your production machine to Insider Fast?

magilla · 16 Jan 2020

Wannagofast said:

Update from 18363.592 to 19546.1000 done and dusted using ISO from UUPDump.
New Nvidia driver 450.12 installed. Other than that, I see nothing unusual to report.

peace
wanna

Huh? Say what?

- - - Updated - - -

Interesting to note that my computer showed downloading 0% all the way through and finally flagged me that it was ready to restart with the big blue banner and I restarted and voila, I have the new build.

Wannagofast · 16 Jan 2020

f14tomcat said:

You took your production machine to Insider Fast?

I use the same setup for everything I do. I have images of all with Macrium Reflect.

I use it to switch back and forth to whatever install I am in the mood to play with. :)

peace
wanna

f14tomcat · 16 Jan 2020

Wannagofast said:

I use the same setup for everything I do. I have images of all with Macrium Reflect.

I use it to switch back and forth to whatever install I am in the mood to play with. :)

peace
wanna

Gotcha.....

neveready · 16 Jan 2020

Went the WU route and to my surprise Stardocks Deskscapes doesn't function on 190546.1000 as it hasn't on the past 3 builds. there fore it will be back to build 19041.1. Better luck next time I guess

Bench Virgin · 16 Jan 2020

Downloading

neveready · 16 Jan 2020

Got 19546.1000 installed using the WU. Deskscape animated backgrounds still show up as a black screen. Reverted back to 19041.1000. will just have to wait for MS to try harder.

smactilactus · 16 Jan 2020

Everything finished up in about 25 minutes. Nothing special so far...

From the thread of the last build...

CountMike said:

It's R7 3700x on Asus prime x470 pro. Are you dual booting regular and insider versions on same disk ? Mine are on separate SSDs but still set up in dual BOOT and have separate MR backups for each. Didn't have any problems restoring each one separately.

I have one build on Fast ring, and one on the Slow ring, normally. And yes, they are on two different SSDs (EVO 960; FORCE MP600). HOWEVER, I finally found the culprit!!!
I cool my 3900X with a NZXT Kraken X72 360mm AIO. And it turns out that this coolers software called CAM, stops RM from initializing... Lol. Why can't our computers be smart enough to tell us something like that in plain language???? As I was rebuilding the other OS, after loading every three apps or so back to the sys, I'd try to start RM. And it would start every time, until I got to the NZXT software, which is normally one of the last things I add. Then I got the same old error message. So I deleted the CAM software, and RM started again perfectly. Then I reinstalled the CAM software, and checked to see if I had it installed, but just unloaded it from taskbar, could I start RM? And I could!!! So problem FINALLY solved, and sys restored to its blazingly fast operations. But this one had me on the ropes for quite a while...
Thanks again for sticking with me, and offering information to help me resolve this.

- - - Updated - - -

jimbo45 said:

Hi thereI tried -- what you get is "You cant keep programs etc because you are running a newer version of Windows"So Restore is the only option --Not sure why that would be a problem in any case --surely people do backups before "upgrading". With sensible windows partition sizes and SSD's a backup / restore shouldn't take more than at the most 15 mins - probably less.
Cheers
jimbo

Yeah, the problem was every time I used the back up, the same problem appeared, which has me assuming it was something with the newer builds. That's why I was looking for another option. Turned out to be a software clash from my AIO cooler's software, which automatically updates itself. So I had not noticed the new update a few weeks back. Thanks.

martyfelker · 17 Jan 2020

Downloading now. I will let it run overnight. Sleepytime.
,
Not quite. First, a Shared VM which had been paused was ready for a restart. Next, this is going fairly fast so I might as well just reboot the physical machine.

Situation understood. The VM was actually ready to restart in 19541. It is working on 19656 (downloading now). I suspended it and am going to restart the physical instance into 19546, See you on the other side.

FAILED and reverted back to 19541 after the 30% completed reboot. The VM seems to have resumed downloading the update which in fact it should. We will see tomorrow how that goes. I'll be seeing whether I can find a log of the failure tomorrow as well. Goodnight for now - hope others have had success.

Virtual Machine completed successfully. Interestingly I did not notice a reboot after Configuring 0 it went directly to 75% updating and finished. I believe I will temporarily change the boot order of the physical so the first hard disk is the Windows Boot Manager rather than Grub. If that works I'll change back to Grub. If it does not I'll boot Ubuntu and grab the UUPDUMP ISO which should do the trick. Sometimes best if Windows doesn't know about other boot loadfers.

SUCCESS. Installing Fast Ring instance using VB 6.1.2 and then Imaging and I'll start working with the Linux distro tomorrow.

bordi · 17 Jan 2020

74 minutes to desktop
With the inordinate length of time delay of 30 minutes on Status: installing - 79%...