Jump to content

WinNTSetup v5.3.5.1


JFX

Recommended Posts

sorry, I really do not know what the problem might be, now I am typing from a fresh 15gb which has rambooted ok, so I believe it must be something to do with the vhd reducing process. have I deleted the wrong file? if so, what is the wrong file. could it be some math against the geometry of the vhd that I am not aware of?

Link to comment
Share on other sites


On 12/7/2023 at 2:11 AM, click-click said:

 

I finally have a single Win2Go flash that will boot on either Legacy BIOS or UEFI hardware. My problems started because I was on Win8 when I tried this. Win8 would not recognize the 2nd partition. On Win10 things went better, but I ended up with a blinking cursor in legacy mode. When I selected the boot drive with Winntsetup, I noticed that the MBR was yellow so I re-did the flash partitions with Bootice which made MBR PBr and Boot partition show up green. I then updated the bootfiles and BCD with Winntsetup. This fixed everything except for the bootmgr menu not showing in UEFI mode. I have 2 VHDs on the 2nd partiton so I can choose either W10 or W11 for booting. BIOS mode shows the bootmgr menu whereas UEFI mode didn't. I fixed this by selecting the checkbox 'display boot menu' in the UEFI BCD. I did not have to do this with the Legacy BCD, so I have no clue why UEFI does not automatically show the boot menu when the UEFI BCD has 2 boot entries listed.

Edited by click-click
Link to comment
Share on other sites

Do I understand correctly that the filter algorithm described above also works on *.manifest files?
Now the records look like this (only a part, in reality there are many of them), 2 pieces *.manifest

WinSxS.ini
\Windows\WinSxS\Manifests\amd64_microsoft.activedirectory.management_31bf3856ad364e35_10.0.17763.1_none_095c3cc5ce4cc481.manifest
\Windows\WinSxS\Manifests\amd64_microsoft.activedirectory.management_31bf3856ad364e35_10.0.17763.1490_none_6621891b47f3382c.manifest
\Windows\WinSxS\Manifests\amd64_microsoft.grouppolicy.management.interop_31bf3856ad364e35_10.0.17763.1_none_45ae278e67e884d4.manifest
\Windows\WinSxS\Manifests\amd64_microsoft.grouppolicy.management.interop_31bf3856ad364e35_10.0.17763.1697_none_a25d3493e19fe3c8.manifest
\Windows\WinSxS\Manifests\amd64_microsoft.grouppolicy.targeting.interop_31bf3856ad364e35_10.0.17763.1_none_6654ff116d4c49a0.manifest
\Windows\WinSxS\Manifests\amd64_microsoft.grouppolicy.targeting.interop_31bf3856ad364e35_10.0.17763.1697_none_c3040c16e703a894.manifest
\Windows\WinSxS\Manifests\amd64_microsoft.remotefilesystems.dfsrhelper_31bf3856ad364e35_10.0.17763.1_none_bdf10eb77895087e.manifest
\Windows\WinSxS\Manifests\amd64_microsoft.remotefilesystems.dfsrhelper_31bf3856ad364e35_10.0.17763.1697_none_1aa01bbcf24c6772.manifest
\Windows\WinSxS\Manifests\amd64_microsoft-activedir..y-webservices-setup_31bf3856ad364e35_10.0.17763.1_none_644bcd2a4e82b8e8.manifest
\Windows\WinSxS\Manifests\amd64_microsoft-activedir..y-webservices-setup_31bf3856ad364e35_10.0.17763.1697_none_c0fada2fc83a17dc.manifest
\Windows\WinSxS\Manifests\amd64_microsoft-windows-a..replicationprovider_31bf3856ad364e35_10.0.17763.1_none_111531154195c448.manifest
\Windows\WinSxS\Manifests\amd64_microsoft-windows-a..replicationprovider_31bf3856ad364e35_10.0.17763.1697_none_6dc43e1abb4d233c.manifest
\Windows\WinSxS\Manifests\amd64_microsoft-windows-a..ry-wmitrustprovider_31bf3856ad364e35_10.0.17763.1_none_ee1a1b5fcc55f884.manifest
\Windows\WinSxS\Manifests\amd64_microsoft-windows-a..ry-wmitrustprovider_31bf3856ad364e35_10.0.17763.1697_none_4ac92865460d5778.manifest
\Windows\WinSxS\Manifests\amd64_microsoft-windows-a..y-delegation-wizard_31bf3856ad364e35_10.0.17763.1_none_efbc5adbce6f3e21.manifest
\Windows\WinSxS\Manifests\amd64_microsoft-windows-a..y-delegation-wizard_31bf3856ad364e35_10.0.17763.1697_none_4c6b67e148269d15.manifest

Is it possible to make the filter output not one, but both files? Like this
\Windows\WinSxS\Manifests\amd64_microsoft.activedirectory.management_31bf3856ad364e35_10.0.17763.*

This would be convenient in the future after the update. And so after the update you will have to rewrite the files to the new version.

Or add some kind of switch to the line to allow 2 files to be displayed, not just one

Thank you

Edited by sakatgg
Link to comment
Share on other sites

The filter

\Windows\WinSxS\Manifests\amd64_microsoft.activedirectory.management_31bf3856ad364e35_10.0.17763.*

matches for both:

\Windows\WinSxS\Manifests\amd64_microsoft.activedirectory.management_31bf3856ad364e35_10.0.17763.1_none_095c3cc5ce4cc481.manifest
\Windows\WinSxS\Manifests\amd64_microsoft.activedirectory.management_31bf3856ad364e35_10.0.17763.1490_none_6621891b47f3382c.manifest

Every wildcard filter will only keep the newest component (17763.1490), all older we be removed.

Whats are you trying to accomplish with all these files?

Link to comment
Share on other sites

Server 2019, these files are needed for the Role Active Directory and DNS server to work, and 2 versions of manifest are needed.
Active Directory and DNS server are not installed with one manifest version

I have 62 manifests that must be 2 each, the rest - 1 last manifest is enough, which the filter leaves

It may be possible to make a key (for example, at the beginning of a line) with which to set the filter - leave one last manifest or both versions

You can check it yourself, just delete even one manifest from the list above and Role Active Directory will not be installed, there will be an error

 

 

 

Edited by sakatgg
Link to comment
Share on other sites

Yeah, installing optional components isn't supported with default minwin profile.

Replace Tools\x64\WIMHost.exe

If you add a ! at line begin it should keep all version.

 

Edited by JFX
Link to comment
Share on other sites

1 hour ago, wuliyen said:

How to keep all files in \Windows\WinSxS\FileMaps?

Not, possible with the WinSxS.ini.

These folder are always deleted:

\Windows\servicing\LCU
\Windows\WinSxS\Temp\InFlight
\Windows\WinSxS\Temp\PendingRenames
\Windows\WinSxS\Backup
\Windows\WinSxS\FileMaps

They should be only needed by Windows Update.
I'll rethink the last 4, maybe add an option for this.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   1 member

×
×
  • Create New...