Windows 10 Insider Preview Fast Build 19564.1000 - February 12 Insider

jimbo45 · 13 Feb 2020

martyfelker said:

Hi there
For VMWARE WKS to get 16:9 resolution (1080X1920) on Linux VM's on Windows HOSTS on this build (works for the most popular distros) the XRANDR method doesn't work properly --- simply use X11-XORG rather than WAYLAND at the logon screen and set the VMWARE menu in view to AUTOFIT Guest.

E,g CENTOS 8 : as VM on this build as HOST

Windows 10 Insider Preview Fast Build 19564.1000 - February 12-d1.png

cheers
jimbo

bordi · 13 Feb 2020

thomaseg1 said:

About the same

did you get a kb4541091 cu for windows 10 next(10.0.19564.1005)

today?

Just got it now, only took a few minutes

jimbo45 · 13 Feb 2020

Hi folks

apart from the VMWare issue (screen resolution limitation on some VM's) this build seems to work just fine as a HOST.

Cheers
jimbo

sysprg · 13 Feb 2020

kado897 said:

That's the slowest for a long time. Nearly 2 and a half hours and I've still got the CU to do.

It depends on the hardware: three lines at the bottom corresponds to my old Thinkpad R500 and previous ones to the bought in 2017 Thinkpad P51.

Windows 10 Insider Preview Fast Build 19564.1000 - February 12-19564-durations.png

kado897 · 13 Feb 2020

sysprg said:

It depends on the hardware: three line at the bottom corresponds to my old Thinkpad R500 and previous ones to the bought in 2017 Thinkpad P51.

My normal time assuming no bouncing is between an hour and an hour and a half. I'm not limited by download speed( 200Mb/sec). I'm running in a VBox VM with 50% of an i7 and 3MB RAM allocated and virtual disk is on an SSD. It should not be taking two and a half hours with no sign of any problems during that period. Every stage was slower than usual, download, Install, getting things ready before restart, and after the restart too.

sysprg · 13 Feb 2020

kado897 said:

Every stage was slower than usual, download, Install, getting things ready before restart, and after the restart too.

My practice differs yours, upgrade of the same systems at 19559 proves it:

Windows 10 Insider Preview Fast Build 19564.1000 - February 12-19559-durations.png

R500 has 8 Gb RAM, 2 SSDs, I5 processor. P51 has 32 Gb RAM, two Samsung NVMes + Samsung 1 Gb SSD, I7 processor

citrixscu · 13 Feb 2020

Fired up a VM in VMware Workstation 20 H1 preview (since I'm using WSL2 on host) to test this out. Upgrade from release failed until I realized that this build, and maybe some before?, does not recognize SCSI virtual disks within VMW workstation. Confirmed by installing fresh from UUP and no disk detected. Changed disk type to SATA and things are fine.

goatty2 · 13 Feb 2020

downloaded and installed took 3hrs even connected by cable instead of wifi.
so far no problems

martyfelker · 13 Feb 2020

bordi said:

Just got it now, only took a few minutes

Yes I got it first thing I got to my desktop

f14tomcat · 13 Feb 2020

jyusa said:

OneDrive won't start

Anybody tried this yet?

sgage: I am unable to manually start the OneDrive app on my PC that syncs with the cloud. The little 'circle of progress' shows for less then a second, then... nothing. Any ideas?

I've occasionally had this happen also, where I click the tile or shortcut and nothing happens. You could try two things.
1) reset Onedrive. Win+R, type - %localappdata%\Microsoft\OneDrive\onedrive.exe /reset It may take a minute or two for icon to reappear. This will totally resync all your content so it may take a while.
If the icon does not reappear after reset and 5 mins, then force it by Win+R, type - %localappdata%\Microsoft\OneDrive\onedrive.exe then OK
2) r-click system tray icon, then Settings, then Account tab. Click 'Unlink this PC' You'll be prompted to set up your account again with your MS sign-in as if you're a first time user.
Good Luck

Also to Nick @swarfega, yes I did. Did nothing but the same for me. Just flat out refused to start to a point where there was any UI at all to work with. Just spin, spin, spin.

I did finally find a solution. I took my ISO I had made and did a nice clean install. 20 minutes later, I had a working 19564 with a working OneDrive. All nice and pristine. Now, I can mess it up again!