WinNTSetup v5.4.1

[alacran]

@Jamdo

You don't need to read all the 9 pages of that topic mentioned by our friend Jaclaz.

Read this 3 posts, all info you require is there:

Building your MinWin:

http://reboot.pro/index.php?showtopic=22621&page=8#entry221675 

http://reboot.pro/index.php?showtopic=22621&page=8#entry221680

Testing Differential VHDs made from MinWin installations:

http://reboot.pro/index.php?showtopic=22195&page=2#entry221689

alacran

Edited September 8, 2022 by alacran

[jaclaz]

For the record your friend jaclaz meant to point to the whole thread (as he actually did), not to your specific posts that are "latest" but that imply already some experience with the tools involved.

jaclaz

[KaMyKaSii]

What I need to do? The error means "Installation disk not valid" but searching this in the thread returns nothing useful. I also want to ask the dev to add a option in the program to the user choose the program language instead of forcing current system language and also a button to update avaliable disks without assuming the user knows that they need to press F5 to do so. Thanks

Edited September 9, 2022 by KaMyKaSii

[JFX]

The boot partition has no file system, format it to FAT32.

For the language add this to WinNTSetup.ini

[Options]
Lang=1033

Or a name of any file inside LANG folder.

[alacran]

JFYI

After making several failled intents to Ramboot Differential VHDs by means of grub4dos for UEFI, this is the answer got from yaya to the issue report made in GitHub page of grub4dos:

Issue: https://github.com/chenall/grub4dos/issues/379

Answer: https://github.com/chenall/grub4dos/issues/379#issuecomment-1258001726

Quote

G4E once realized the first level difference, but it has no practical use, just an experiment. This function has been removed in the new version. No longer supported!

Differential VHDs are not directly supported anymore in G4E.  So no way to Ramboot them.

Only option remaining in grub4dos to filedisk boot differential VHDs (in MBR and UEFI), is by means of using the external command ntloader.

alacran

Edited September 27, 2022 by alacran

[enuser2k]

JFX

After applying MinWin for Windows 11, the modern control panel does not open. Also, Personalization and Display Options in the desktop context menu do not open. Managed to figure out how to fix it. You need to copy the following dlls from the original image to C:\Windows\System32\
- SwitcherDataModel.dll
(is responsible for the initial call to the control panel)
- ServicingUAPI.dll
(responsible for displaying the content of the control panel)
- SettingsHandlers_Gpu.dll
(display options)
- SettingsHandlers_OneCore_BatterySaver.dll
(power options)

So far, these errors remain:
volume in tray not working (need to find appropriate dll for it)
calendar in tray not working (same)
explorer crashing when trying to change wallpapers (same)

MSI Afterburner not working (if anyone has managed to get it up and running, please let me know how).

Edited September 28, 2022 by enuser2k

[JFX]

Thanks for these files enuser2k 

I have not done much with Windows 11, but the volume and calendar tray is working with classic taskbar using StartAllBack.

MSI Afterburner needs the 2008 VCRuntimes (both x86 and x64).
Seems I broke these installers, will be fixed.

[enuser2k]

JFX

Yeah, with StartAllBack classic taskbar, volume and calendar tray is working.

As for C++ Runtimes, all versions are installed except 2008, as you said.

Also, in order to set wallpapers, you need to copy Windows.Management.Workplace.dll (not sure about Windows.Management.Workplace.WorkplaceSettings.dll).

And I forgot to say, if dlls are copied on a live system, you need to reboot the OS.

[JFX]

Found the VCRuntime dependencys.

\Windows\System32\sxsstore.dll
\Windows\System32\config\TxR

Not so easy to track, if it's a folder which is required.

MSI Afterburner shows an error messages when closing.
But I'll will not add fix for this in default profile.

\Windows\SysWOW64\taskschd.dll

[enuser2k]

JFX, Awesome!

And I don't have any errors when Afterburner closes. Btw, I just created an empty folder TxR, without copying its contents.

2 hours ago, JFX said:

Not so easy to track, if it's a folder which is required.

It's true, it's like the "C:\Windows\Installer" folder. It should be there, even empty. If you remove it, any msi installers will not work.

Edited September 30, 2022 by enuser2k

[Antonino]

excuse me, I would like to know how to signal my intention to get rid of a certain filetype wherever it is found on the os disk/vhd, of course by a script string of this kind:

\*.kyk\*

or

\*.scr\*

are they correct?

oh before I forget, is there any such thing as custom_command.txt, like in win_reduce_trusted, where one can place any string he/she sees fit?

if there isn't one, can I append strings to any list I find, or do I have to use a specific script for them to be effective?

tx in advance.

 

                                                                

Edited October 7, 2022 by Antonino
just happened to close the hatch unintentionally before finishing the post

[JFX]

Hi Antonino,

a line like "\*.kyk" will remove all files that match *.kyk and are not part of any whitelist.

As for custom_command, no currently there are none. Give me some examples, so I know what these commands need.
I mean I can add needed environment variables like %tempdrive%, %minwinprofile% or %OSBuild% before execute them commands.

[Antonino]

so will those files be removed from across the whole volume, regardless of where they are found?

my second question was related to a group of system32 and syswow64 root files that I have to keep in order to let my favorite software still work after the miniwin deletions. so I was thinking of as many instances of !\windows\system32\filename.dll and !\windows\syswow64\filename.dll as my files to keep to be appended to system32-dll.txt and syswow.dll respectively. but just in case I place these strings elsewhere, in some other scripts, will they be effective, viz, will the files be kept where they are even if the instructions are not in the proper textfile? 

do u mean environment variables make the operation handier and more viable? 

Edited October 7, 2022 by Antonino

[JFX]

11 hours ago, Antonino said:

so will those files be removed from across the whole volume, regardless of where they are found?

Yes, it will scan the entire drive.
 

11 hours ago, Antonino said:

my second question was related to a group of system32 and syswow64 root files that I have to keep in order to let my favorite software still work after the miniwin deletions. so I was thinking of as many instances of !\windows\system32\filename.dll and !\windows\syswow64\filename.dll as my files to keep to be appended to system32-dll.txt and syswow.dll respectively. but just in case I place these strings elsewhere, in some other scripts, will they be effective, viz, will the files be kept where they are even if the instructions are not in the proper textfile? 

Name of the *.txt file does not matter. Best to create a new "MySoftware.txt" that contains the whitelist or this specific software.

 

About custom_command.cmd in win_reduce_trusted you only get the driveletter as %WorkDrive%.
There could be added much more information... 

[Antonino]

thank you ever so much for ur detailed reply, jfx. so, if i have understood correctly, winntsetup is already prepared to accept instructions from a file called MySoftware.txt if it finds it in the \Tools\MinWin\Default\Remove folder, right?

Edited October 8, 2022 by Antonino