[DISCUSSION] Windows 10 1903/9 'FINAL' Build 18362/3.xxx (PC) [19H1/2 Release]

I already have tried that with Regshot many times ago, not able to find/pinpoint any precise reg change, so asked here.

 

You need to restart the Windows Search service or restart the computer for the change to be applied.

I took this setting directly from my server's GPO registry template.

 

You need to restart the Windows Search service or restart the computer for the change to be applied.

I took this setting directly from my server's GPO registry template.

 

Here I am talking about integrating that regfile directly in and with Win ISO so that it can be applied since the very first boot of Windows on a clean installation, which, again, as I said earlier, didn't happen so I am looking for the correct solution.

 

Here I am talking about integrating that regfile directly in and with Win ISO so that it can be applied since the very first boot of Windows on a clean installation, which, again, as I said earlier, didn't happen so I am looking for the correct solution.

 

And here I am saying that either the Windows Search service, or the device itself, needs restarted. Just because you set a registry property in an offline registry hive does not mean it is applied during the first boot. There are many registry keys and property values that can be set in offline hives and still require a first reboot after deployment.

Moreover, this registry setting is applied to all my MDT deployment WIM files for 1903 and do set Windows Indexing to Enhanced Mode.

 

I am not going to keep replying to you in two separate threads. I know exactly what you wrote and my previous post still reflects that.

 

This is the correct implementation.

 

OK then, I will try once again, am sharing the reg file here, can you take a look & confirm whether it's good or need further modification?

 

Shall I save that command as a .BAT file and run it as admin?

 

.cmd will work.

 

Yes, Thank You.

 

Hello everyone,

I'm using UUPdump default scripts to create 18362.295 and 18363.356 WIN10 PRO ISO files.
I'm doing that on a 18362.267 version of Windows, with no errors.

In Rufus (v3.7) however I can't burn the 2 respective ISOs on a FAT32 formatted drive.
It auto-selects NTFS and won't allow me to change it.

I don't remember that being the case for .267 and below versions.
FAT32 & non-CSM UEFI worked just fine.

Am I doing something wrong or is this normal for .295 and .356?



P.S.

I encounter plenty of errors using the very same scripts on another 18362.295 - updated via WU to 18362.356 - Windows machine.
But that's a different topic.

 

Rufus makes it NTFS when the ISO is too big to fit onto a FAT32 formatted drive. FAT32 has size limitations regardless how big the drive is.

If you convert the install.wim to ESD you can use FAT32 again.

You can change an option in the UUP Dump script .ini file so it coverts to ESD but can take a long time to do so.

 

Recently @abbodi1406 set the cleanup to disabled for 1903/1909, now the iso's are quite a bit larger, if you want it to fit fat32, either change the convertconfig.ini to cleanup and or set it to create an install.esd.

You could also use this "simple to use" tool, to do it afterwards: Windows 10 ISO With Install.esd/Install.swm Creation Tool

 

Thank you both for replying, KedarWolf & Enthousiast.

WIM or ESD don't really matter for me.

I was just trying to understand if I'm at fault or some things changed.

Glad to find out the latter is true.

 

Here is an overview of the different sizes to expect with the different cleanup settings:
https://forums.mydigitallife.net/th...10-uups-with-ease.75052/page-144#post-1546989

 

Thank you, I will give it a read.
I don't really know what this "cleanup" is all about but sounds interesting.

Just noticed that my .267 machine decided to update itself to .295 via WU.
I postponed the restart so I could create more ISOs of past versions, .267 and before.

That is because I couldn't complete a single UUPdump script on the other .295 machine, no matter what ISO version I chose to create.

In that respect, is there any way to deny Windows 10 Pro the chance to auto-update itself?

 

Pause update from Windows Settings

 

Please; Tell Me: When Will The New Version of Windows 10 Version 1909 Be Available?
1909 = 2019 September?