KB4100375 Windows 10 Insider Release Preview Build 17133.73 - Apr.10 Insider

magilla said:

Yes, I think I'll wait. Although the version of windows I have is 17133.1 (1803)--Did a clean install a couple of days ago and that is what I have

I am in no hurry to get an ISO.

You can edit your post and delete the attachment and crop it.

reposted without account name. Thanks Josey.

No, I guess this is not the RTM. I have same winver on all my computers.

So there I was, trying to RDP into 17133 from my tablet. I could RDP to Skippy and FCU but not 17133. I spent ages, checking settings etc, and finally dawned on me why. It is amazing how you miss the obvious!

With FCU and Skippy, I was l
auto logging in with MS Account (using netplwiz). I was convinced it was a bug.

With SCU, I was using a local account with no password set and of course, RDP will not work if remote pc does not have a password.

It will work with MS account and netplwiz (you still have a password but just do not need to enter it).

So changed to MS account, and used netplwiz, and karma has been restored :-D.

cereberus said:

So, I tried to upgrade my 32GB mmc, 32bit tablet to 1803, and run into dreaded need 8GB message, and inserted a flash drive and it just kept failing. Short of deleting stuff, I could not see anyway to sort this.

Being a stubborn person, I thought how about making image backup with Macrium, restoring that to Hyper-V in a larger vhd, do upgrade, and do disk cleanup until C drive is below 32GB (with a bit of margin), and restore it to tablet.

Sounded fine but I had forgotten Hyper-V does not allow 32bit uefi vms.

Now I thought hard about this, and created a legacy bios gen 1 vm, and installed 1709 windows first.

I then restored C drive from tablet backup over the new 1709 installation, and it would not boot if course.

I then ran Macrium "fix windows boot problems" option and then it booted ie I has turned a 32bit uefi install into a 32bit legacy bios.

I then upgraded the vm to 1803, and did disk cleanup etc, and now I was at around 28GB.

Then I imaged the C drive only with Macrium andcrestored it to tablet deleting original C drive partition, and as I expected it would not boot until I ran Macrium "fix windows boot problems", and then it worked.

If tablet is 64bit uefi, life is much simpler, as you do not need to mess around with legacy bios installs, and recreating bcd.

As an interesting aside, I was a little surprised I did not have to mess around with the boot files as legacy bios always used different ones to uefi, but when I examined the boot files being used by legacy bios, it was using the SAME files used by UEFI - in fact the boot files have a .efi extension. It seems MS have changed something so same boot files can be used in legacy bios or uefi, and all you need to do is rebuild bcd.

This is good food for thought. I have a friend who, along with his wife, have a pair of laptops in this configuration that are running into the 8 GB threshold on their machines.

Might have to explore doing something similar to this for their machines once SCU is 'officially' released.

johngalt said:

This is good food for thought. I have a friend who, along with his wife, have a pair of laptops in this configuration that are running into the 8 GB threshold on their machines.

Might have to explore doing something similar to this for their machines once SCU is 'officially' released.

It is easier than it sounds once you have sussed out the sequence. This can be done using any Virtual Machine.
I believe it is possible to install 32bit UEFI in VMware - if so sequence is simplified as for 64bit sequence below.

In simple generic terms for 32bit UEFI installations on VMS that cannot boot 32bit UEFI

1) back up tablet with Macrium Reflect

2) Clean install FCU Windows as LEGACY BIOS in a vhd larger than 32Gb e.g. 60GB

3) Restore C partition from tablet image over clean installed C partition

4) Run Macrium Reflect "Fix window boot problems"

5) Expand C drive to fill all space on VHD

6) Upgrade installation

7) Do disk cleanup etc. - check installed files less than say 30 GB

8) Image backup C partition

9) Restore C image partition to tablet, over writing C partition

10) Run Macrium Reflect "fix windows boot problems"

If device has 64 bit UEFI install or (VM supports 32bit UEFI), the sequence is rather simpler

1) back up tablet with Macrium Reflect

2) Restore Macrium image in a vhd larger than 32Gb e.g. 60GB

3) Expand C drive to fill all space on VHD

4) Upgrade installation

5) Do disk cleanup etc. - check installed files less than say 30 GB

6) Image backup C partition

7) Restore C image partition to tablet, over writing C partition

8) Run Macrium Reflect "fix windows boot problems"

1803 seems to be impossible to download (at the moment, at least) using UUP Dump:

magilla said:

Yes, I think I'll wait. Although the version of windows I have is 17133.1 (1803)--Did a clean install a couple of days ago and that is what I have

I gonna wait too, Magilla. When Microsoft finally releases the final to us, I'll clean install it to my RTM Partition.

rogerwilco91 said:

... it would make sense to release a major update on Patch Tuesday...

The public launch of 1709 was on 17th October, one week after Patch Tuesday. My money is on April 18th.

Wynona said:

I gonna wait too, Magilla. When Microsoft finally releases the final to us, I'll clean install it to my RTM Partition.

Yeah, @Wynona. I don’t get all the hubbub trying to be first to have this build. I think we have 99.99 % of it already. I know for many of us it’s the challenge of it all, but I’m not feeling very challenged at this time.

Kari said:

1803 seems to be impossible to download (at the moment, at least) using UUP Dump:

I just checked for en-us - same error.

But I already have the .ISO for said build. I know that doesn't help you much, but I'll keep trying to see if it comes back.