Windows 10 Insider Preview Fast Build 19551.1005 - January 23 Insider

Using Fedora Rawhide w/ kernel 5.5.0-0.rc6.git3.1.fc32.x86_64 created instances of this build using VMware Ws 15.5.1, VirtualBox Version 6.1.2 r135662 (Qt5.6.1) and Virtual Machine Manager (QEMU/KVM). The last runs concurrently with VMware but not with VirtualBox. On to openSUSE

- - - Updated - - -

Have gotten VirtualBox 6.1 and QEMU/KVM working on openSUSE Tulmbleweed kernel 5.5.0-rc7-2.g7193c66-vanilla. VMware is installed and appears OK except I run into an unusual problem, which hopefully somebody here might have some idea about. The virtual machine (in this case this build) appears to installed up to the point where the hard drive is going to be created but then there is no hard drive! I think openSUSE may be the only distro I'[[ve seen this happening but I've definitely seen it before and have no clue. No quick Internet search yields results. What I'm going to do however is copy a VM from another distro and see whether I can open it ... yes that works. Was able to copy a paused Shared VM to my home vmware directory and resume it. The problem is very strange but hey ...

- - - Updated - - -

I have gotten gnome-boxes to work on Fedora Rawhide. This makes 4 different virtualization solutions for Fedora.
The VM is only 20GB in size - after creation, there was almost 10GB free. Compressing the drive btw saved no space.

What I find extremely annoying is that Volume Mixer at restart always resets the volume of all apps and browsers to same, default level.

I have my reasons to use different volume levels on different apps, and until a few builds back, it had always worked. An example: My main browser is and has been since October 2014 the Edge. I only use Maxthon browser to be always connected to online services from my native Finland, to check the news and so on. My default volume level is set to 50, and because quite a many of those Finnish news sites I daily read use autoplaying videos and video ads, Maxthon's volume has always been muted, level was set to 0.

That worked, as I said. But now, after every restart, Maxthon's volume level is reset to default. I have to change volume levels of several apps and browsers each time I start the PC.

Earlier, these settings were kept intact, and my Maxthon always started with volume completely muted:



Today, last three or four builds, it starts like this. All application dependent volume settings reset to default volume level:



Is it just me, or is anyone else experiencing the same?

Kari

Kari said:

What I find extremely annoying is that Volume Mixer at restart always resets the volume of all apps and browsers to same, default level.

I have my reasons to use different volume levels on different apps, and until a few builds back, it had always worked. An example: My main browser is and has been since October 2014 the Edge. I only use Maxthon browser to be always connected to online services from my native Finland, to check the news and so on. My default volume level is set to 50, and because quite a many of those Finnish news sites I daily read use autoplaying videos and video ads, Maxthon's volume has always been muted, level was set to 0.

That worked, as I said. But now, after every restart, Maxthon's volume level is reset to default. I have to change volume levels of several apps and browsers each time I start the PC.

Earlier, these settings were kept intact, and my Maxthon always started with volume completely muted:



Today, last three or four builds, it starts like this. All application dependent volume settings reset to default volume level:



Is it just me, or is anyone else experiencing the same?

Kari

Have the same problem with AMD Software always reverting to default after each new flight....messing up my preferred setup.

Update:

Windows 10 SDK Preview Build 19551 now available - January 28

Announcing Windows Server vNext Insider Preview Build 19551 - Jan. 28

Bench Virgin said:

Just got this .

Hello mate,

Unlike usual, Windows 10 19551.1005 has incorporated cumulative updates. The KB4538791, KB4538792, KB4538793, KB4538795, and KB4538794 as a dynamic update.

Brink said:

Hello mate,

Unlike usual, Windows 10 19551.1005 has incorporated cumulative updates. The KB4538791, KB4538792, KB4538793, KB4538795, and KB4538794 as a dynamic update.

Just thought I'd add this informative link

Microsoft explains how Dynamic Updates work on Windows 10 - gHacks Tech News

UPDATE:

New known issue added.

[ADDED] There is an issue impacting ARM64 devices from updating to this build successfully. A fix will be coming soon in a future flight.