Windows 10 Insider Preview Fast Build 19541 - January 8 Insider
-
Thank you LEOPEVA64. I missed that!
This is fustrating as Outlook search broke in 19536 and MS have had plenty of time to scope any fix in this 19541
I'll sit this one out!
-
-
I think I remember part of the scenario. 19036 was screwy. Going back to 19031 (I think) and updating was the trick.
Went back to 19035, did a clean install and then 19541 installed fine. Thank You.
-
Went back to 19035, did a clean install and then 19541 installed fine. Thank You.
Super! The 'ole brain cells memory bank ain't dried up yet!
-
-
-
Has not appeared yet. There was a notification of an AMD driver which required a reboot but it did not show up history. I expect there will be another build fairly soon which might be more substantial. Maybe I should be running Task Manager more often?
- - - Updated - - -
Downloading in a VM. Somehow lost membership in Insider Program - as soon as I "regained control" started downloading this build. Relize you actually give up some control to MS when you join the Insider program. That's OK since I can fix the problems easily.
-
Has not appeared yet. There was a notification of an AMD driver which required a reboot but it did not show up history. I expect there will be another build fairly soon which might be more substantial. Maybe I should be running Task Manager more often?
- - - Updated - - -
Downloading in a VM. Somehow lost membership in Insider Program - as soon as I "regained control" started downloading this build. Relize you actually give up some control to MS when you join the Insider program. That's OK since I can fix the problems easily.
Hi there
I used UUPDUMP -- I think unless you have a specific need to test the standard update process then IMO the UUPDUMP method is best --beats also joining any insider program. Also if you have more than one machine to update you can use the same ISO on all of them.
Cheers
jimbo
-
Hi there
I used UUPDUMP -- I think unless you have a specific need to test the standard update process then IMO the UUPDUMP method is best --beats also joining any insider program. Also if you have more than one machine to update you can use the same ISO on all of them.
Cheers
jimbo
This can be done without being in The IP?
-
Well loads of posts what has gone wrong but none to say "hey that new feature is cool". Oh sorry, I thought this was the Fast Ring.
-
This can be done without being in The IP?
Hi there
@Josey Wales
absolutely !!! never been a member of insiders and got all these builds.
Also the good thing is that if you say want to revert back to a "Non Insider build" via restoring say a macrium image you won't be marked as being a member of the insider program so you can "Unjoin" at will.
@cereberus -- I think the USB "forwarding / redirection" or whatever it's called seems to work perfectly on this release when "Hot plugging" USB 3 devices from a HYPERVISOR -- certainly it works now when hotplugging USB devices from a KVM/QEMU HOST to this release as a Windows VM -- no need for any action in the VM config file or to attach it via the VM menu -- Device just appears as available in the Windows notification. I always had trouble with USB hotplugging using a HYPERVISOR whether a Windows one (HYPER-V) or a Linux one (QEMU/KVM).
General passthru also to this build on a VM's seems a lot better -- actually WORKS !!! including sound, video hardware capture device etc etc. Even Bridged networking does "what it says on the tin" with full bus speed between HOST and VM rather than at "Network speed".
This VM can also boot from physical USB devices from INSIDE the VM too. So improvements somewhere in the Windows kernel although I suppose a lot won't notice these two features.
This is actually quite a nice feature -- you can boot say a live linux USB distro from INSIDE your VM - useful for fixing Windows problems at times - without having to attach an iso and then boot that. You can also boot a Windows to Go USB from INSIDE the VM too - so some nice stuff to play with.
I never got this stuff working as well before on a Windows VM and I'm sure the Linux packages haven't changed much either so I must assume there's quite a lot changed in the Windows kernel - probably as I said invisible to most people.
Cheers
jimbo
-
-
After install I still get the same error as 19536 0xC1900101 -0x30017 first boot phase error. Lesson learnt from 36 and havent bothered doing anymore re stall tests as its a waste of time, obviously something isnt right with these new builds as its not just my machine.