New Windows 10 Insider Preview Fast+Skip Build 18956 (20H1) - August 7 Insider

Hi there

@dencal

Of course we expect defects etc -- these are probably not even alpha builds -- what though gives me problems is when a basic feature that has been working almost since Windows first started -- I don't know how many years ago --certainly > 20 years surely that should continue to work with the new builds -- I don't mean 3rd party hardware or software - but the basic integral things within the Windows OS such as its configuration screens and display stuff -- if it worked in Language "Z" for example in current ( build - 1) why on earth should those display menus etc appear in a whole hotpodge mixture of languages all hosed up in current build ( + 0 ) or (build + 1) i.e the next one -- or the one we are testing now.

Perhaps developers these days can't be bothered to test what they perceive as "existing functionality" -- yes I know it's not the most exciting job in I.T -- as they assume it will work as "it has already been tested" and just go to test new stuff.

If I were in ANY I.T dept I wouldn't let any developers loose on new projects until they 100% understood REGRESSION TESTING !!!!!!!!.

Thankgoodness for UUPDUMP as also the WU process seems to be totally hosed up -- works for some and totally Bonkers for others --even when judging by the computers a lot of people are using there isn't a massive amount of difference in the basic hardware -- and even if there were surely the Base Windows should install and then allow users to update manually the required drivers etc.

Windows generic drivers will invariably allow a system to boot and connect to the Internet even if the Video is Bonkers etc --- once you've got a booted system you can always fix manually.

If I were in charge of this type of I.T dept - I'd get the developers to check the return code from drivers --if the hardware returns some silly exception then I'd expect them to try any of the Windows generic drivers and if those fail to then skip that section. The OS should always continue to load until it's absolutely hopeless --you'd be surprised on what basic hardware Windows can run on --it's actually quite good on that -- and even though I use Linux a lot I've often used the Windows diagnostics to find out details about problem hardware drivers !!!!.

Cheers
jimbo

On 18956 I noticed yesterday that some of my programs that save data to my "data drives" could not find those drives. It took me a minute to figure out that somehow 18956 changed the letter designation? Changed them back to normal designations and of course all work.

dencal said:

The thing I find so galling with a failed Update….after having taken an hour or more installing.....then states "Undoing changes made"....Reverting back only taking a minute.

Food for thought....If a UUP iso can successfully Update.....WU fails....a possible solution somewhere there?

I can't understand why this problem has continued for so long without a fix. 18956 is the 7th build in series that has refused to install on my Skip Ahead machine via WU. UUPDump download installs via USB drives have been 100% successful.

#2 Insider computer with first try reverting back to 18950. The next try, finally installed. Don't understand why it takes 2 times to finish? Evidently "Feature Updates" can't keep track of what happened.

[QUOTE=martyfelker;1690181]

jimbo45 said:

Hi there

@martyfelker

I think you meant Windows for Workstations -- !!!!!!!!
Yes. Displaying my age a bit with that typo.
Windows for workgroups is really old (Windows 3.11)
I had a CD of that once - disappeared.
Remember :

Attachment 242667

To see performance improvements of Windows 10 Workstation compared with the standard W10 PRO you do need to have good hardware -- dual (or more) processor systems really show it especially if they have hyperthreading on all the cores (in my case 8) enabled.

Yes. I have AMD Ryzen 7 2700X Eight-Core Processor, 3700 Mhz, 8 Core(s), 16 Logical Processor(s)


On bog standard machines You probably won't see much difference - Gamers might of course although Windows 10 workstation is probably more like W10 Enterprise -- also thankfully leaves out a lot of the hideous Bloatware.

No way can I get any VM to work with VMWare workstation on Linux Host with kernel 5.2.6 or 5.3 -- works (with patch) on 5.2.5

Yes, Right now I'm running VMware on Manjaro (lataest stable) with Kernel 5.3rc2. Works fine except no Workstation Server (no shared VMs). Amazingly did not even need the patch - installed from AUR (found instructions on the Web) Also I installed on Ubuntu 19.10 with (I think) 5.3rc1 with patch from Github. Ubuntu did support the Workstation Server.

However installed standard W10 for Workstations on my normal laptop -- perfect. I can't really use this build as a VM even on a Windows Host as I can't get Bridged Networking to work with this build tried VBOX as well --hideous compared with VMWare (IMO) -- same problem -- that's a showstopper for the VM -- I've got another spare machine but I don't want to mess it up so Il created a "Windows to Go" system for continuing to test this build on until issues with VM's and Networking fixed. Got the W2GO system on external fast USB (3.1) -->SATA connection so performance is fine.
Virtualbox on Manjaro - installed Windows 10 for Workstation but it's pretty poor compared with VMware.
Experimenting with XEN and KVM as well -- but for messing around with VM's and fiddling with hardware VMWare IMO is the only practicable option as you don't have Driver problems (normally !!!!) and can usually load specific eseoteric hardware drivers directly into the VM which is a pain if using HYPER-V (if not impossible) or other HYPERVISORS.

If you got VMWare to work with kernel 5.2.6 or higher - what did you do and what distro.
See above,
Cheers
marty

I hope the interpolated replies worked out. Update: Screenprint of my first Hyper-V VM (Ubuntu 19.10 w kernel 5.3rc3), It runs very fast but I have yet to figure out how I can remotely logon in order to (supposedly) use my host sound card.

Hi there

@martyfelker

I think that's one of the limitations of using HYPER-V -- getting these sorts of devices to work is not as easy (if at all possible) compared with using VMWare / VBOX.

For Windows VM's on HYPER-V I think you have to use RDP to connect to the VM with the option of carry sound from the HOST machine. I'm not sure if anybody has got Sound working on a Linux VM running on HYPER-V -- that's another issue though.

RDP should work if the VM is set up correctly though.

BTW as far as VMWARE is concerned - my problem was I couldn't get the vmmon module to compile on any release of kernel > 5.2.X for running on a LINUX Host. No problem with running Linux VM's on a Windows Host though.

To logon TO Windows FROM Linux -- install TIGERVNC on the Linux box -- start the server and you'll see a similar screen to Windows RDP screen.

to logon TO Linux FROM Windows install XRDP or similar on the Linux box and then just use RDP on Windows.

Cheers
jimbo