New Windows 10 Insider Preview Fast+Skip Build 18965 (20H1) - Aug. 21 Insider

jimbo45 said:

Hi there


in addition to what others have posted :

I don't think either it matters what you use as as your Virtualisation software -- same type of result whether using HYPER-V, VMWare or KVM -- probably the same if you use VBOX but I've no experience of that. one though.

With Office Pro plus the Visio and Project applications, Photoshop, Kodi, VLC, an ISO from UUPDUMP and some downloaded data my Windows VM is around 18 GB in size (actual physical size on my Host machine) even though I specified an 85GB Virtual disk size -- Virtual disks can be allocated so that they grow when needed up to max size specified. If I discard the UUPDUMP iso and some downloaded data or move it from the VM to host the VM would be approx Kari's size of 11 GB --maybe a teeny weeny bit more (Photoshop and the entire office suite).

Cheers
jimbo

One thing to remember is that when you upgrade to a new build Windows.old can be over 20GB.

Since I couldn't get my Nvidia driver installed on my old HP DV6000, even using DDU, I tried a clean install from an ISO.


Low and behold it installed the graphics driver.

Updated a VMware Workstation 15 that was on build 18963 with an ISO of build 18965 with (KB4517787 and KB4517789) included and it is working good.

Caledon Ken said:

Since I couldn't get my Nvidia driver installed on my old HP DV6000, even using DDU, I tried a clean install from an ISO.


Low and behold it installed the graphics driver.

Clean installs work wonders.

They do but I hope they address. Most just want to upgrade without the clean install pain.

LEOPEVA64 said:

New Feedback Hub app improvements in Windows 10:

And thank goodness! The Upvote system as it was used before was archaic - sort of like the Micro$oft social answers "I have this problem too!" vote - I am sooooo happy they forced it to be like it is now - this has been long overdue.

smactilactus said:

So, nobody on here uses virtual desktops???

I would, but I use my desktop and both my laptops via Mouse w/o Borders, so the lappys are my 'virtual' desktops, sort of. I try to have almost all the same apps on all 3 machines, so if one goes down, even with a full backup some things might be new. so I can copy / paste settings / keys / etc. from the working to the non-working.

I should probably try to start using them, though. Right after I build my new system....

Brink said:

We're excited to announce a refresh of the Windows Insider Achievements page in Feedback Hub: https://aka.ms/AA5wmqd

Be sure to check it out and begin unlocking badges, and send us your feedback with the hashtag #Builds4Badges.

Tweet

— Twitter API (@user) View on Twitter

#%^$%#^#$%^$%^ Badges. How about you stop being a social butterfly, Micro$oft, and start writing better code (that's tested better internally)?

jimbo45 said:

Hi there


in addition to what others have posted :

I don't think either it matters what you use as as your Virtualisation software -- same type of result whether using HYPER-V, VMWare or KVM -- probably the same if you use VBOX but I've no experience of that. one though.

With Office Pro plus the Visio and Project applications, Photoshop, Kodi, VLC, an ISO from UUPDUMP and some downloaded data my Windows VM is around 18 GB in size (actual physical size on my Host machine) even though I specified an 85GB Virtual disk size -- Virtual disks can be allocated so that they grow when needed up to max size specified. If I discard the UUPDUMP iso and some downloaded data or move it from the VM to host the VM would be approx Kari's size of 11 GB --maybe a teeny weeny bit more (Photoshop and the entire office suite).

Cheers
jimbo

One other thing to note - I found out the hard way, at least on older systems - you can't run VBox and Hyper-V simultaneously on X58-based mobos - and the sources I have for that make absolutely no distinction with chipset / CPU, but that is the only chipset I have that I have tried it on, so that's the only one I can say anything about for a fact. However, I found a (basic) script online that I modified to include auto-self-elevating with privileges in order to easily set the Windows 10 HV Launch type (and tried to make it as foolproof as I could) so that you could easily enable HV launch through a bcedit command (it does require a reboot, though, when changing from auto <--> disable. This allows you to disable (to run VBox) and enable (to run Hyper-V) the hypervisorlaucnhtype variable. If anyone is interested I'll post the cmd script, but it's pretty simple.

Kari said:

The best part of installing Windows to VHD and booting to it is that no virtualization software is required. Booting natively to VHD means it uses the real, physical hardware of the host. It is and behaves as any physical Windows installation, with only one difference: Windows cannot be upgraded on native boot VHD.

To upgrade my native boot VHDs, I boot to host main OS, create a Hyper-V VM using the native boot VHD as existing hard disk, and upgrade it using UUP Dump ISO. When upgraded, I can again boot natively to it.

When I no longer need a specific VHD, I simply delete the VHD file and remove its boot menu entry.

Kari

That sounds like grounds for a tutorial ... oh, wait.

johngalt said:

And thank goodness! The Upvote system as it was used before was archaic - sort of like the Micro$oft social answers "I have this problem too!" vote - I am sooooo happy they forced it to be like it is now - this has been long overdue.



I would, but I use my desktop and both my laptops via Mouse w/o Borders, so the lappys are my 'virtual' desktops, sort of. I try to have almost all the same apps on all 3 machines, so if one goes down, even with a full backup some things might be new. so I can copy / paste settings / keys / etc. from the working to the non-working.

I should probably try to start using them, though. Right after I build my new system....



#%^$%#^#$%^$%^ Badges. How about you stop being a social butterfly, Micro$oft, and start writing better code (that's tested better internally)?



One other thing to note - I found out the hard way, at least on older systems - you can't run VBox and Hyper-V simultaneously on X58-based mobos - and the sources I have for that make absolutely no distinction with chipset / CPU, but that is the only chipset I have that I have tried it on, so that's the only one I can say anything about for a fact. However, I found a (basic) script online that I modified to include auto-self-elevating with privileges in order to easily set the Windows 10 HV Launch type (and tried to make it as foolproof as I could) so that you could easily enable HV launch through a bcedit command (it does require a reboot, though, when changing from auto <--> disable. This allows you to disable (to run VBox) and enable (to run Hyper-V) the hypervisorlaucnhtype variable. If anyone is interested I'll post the cmd script, but it's pretty simple.



That sounds like grounds for a tutorial ... oh, wait.

VBox has only recently got support for Hyper V and from all reports it doesn't work very well if at all.

So, I used WU to upgrade all 3 machines - my homebrewed desktop, my Lenovo ThinkPad laptop, and my Dell Inspiron laptop.

Both laptops took an inordinate amount of time to upgrade. I had hte normal "Preparing" section before DL, which seemed to hang at 70% for hours. Then there were the reboots - at least 3 for each laptop. But, in the end, with all of the little problems associated with 18965.1000 (block chars, for one, in Settings --> Devices), they got installed.

The desktop gave me the standard DL --> Installing --> prompt for reboot. After rebooting and letting it install overnight, I came back to the machine early this morning - with a reboot prompt. I thought "That's odd" - so I let it reboot again - it went through the motions, an finally, got to the Setting Windows Up screen - where it hung for 2 solid hours.

I finally had enough and hit the reset button - and now I'm on 18965.1005 but still have the block characters in Settings --> Devices.

Did 1005 fix those block chars for anyone, or is everyone still seeing those?