New
#200
Yeah, I gave up on Hyper-V last year after it simply had too many problems. However, yours and Jimbo's success with either VMware or VBox have gotten me interested in possibly using one of those third party solutions to start running a couple of VMs again, including one for testing WinX WS. Time will tell.
Q: to run VMWare / VBox, do I need to have the Hyper-V components enabled in WinX? I already have the BIOS settings enabled for correct VM use, but I wasn't sure (and wanted to avoid the reboots).
Ahh, I didn't know about this issue because, IIRC, that was right around the time that I was packing and moving into my new home. Or, I knew and had forgotten about it.
Yeah, the revert to an older build is what I am currently completing - I had started having issues with 18945, clean installed 1903 quickly, and upgraded it to 18945, then 18950, and it started having issues again.
So I'm back on 1903 for the nonce, until I am 100% positive I've got it worknig the way I want with all apps / games / drivers installed. Then I make a new full backup, and then attempt to upgrade it to 18956. We'll see how that goes. But, at least my system is working rather flawlessly right now.
If 18956 still causes me issues, I'll just create a VM for the Skip ahead builds for now and see how that goes, until I see a build come across with very few issues reported here in the forums.
I know that language issue has plagued you for a while - glad to see it's working finally as it should.
Several people have reported something similar in the last few builds, about the boot drive showing up with an assigned drive letter in Explorer.
The fix for this should be interesting.
^^^^ This please!
Thanks for the heads up!
@Kari - it sounds like your system could benefit from regressing to an older build and trying to update again - that is too many different issue sot be dealing with when trying to evaluate the build itself, no?