WinNTSetup v5.3.4

[JFX]

You can't change it, but you can add it original form.

[suxichao]

Only the MinWin function of the WinSxS.ini configuration file seems to get stuck in the circle interface and report an error when dealing with 17763 and earlier kernel versions (such as 17134). Should I change the project of Setup=0 in WinSxS.ini to Setup=1? Or are there other better solutions?
I remember when I was dealing with WinSxS a long time ago, I called the NSudo tool to delete WinSxS when I entered the desktop. It takes a lot of time to study the folder items that need to be retained, so I especially admire JFX for making such an excellent solution. Thank you very much, JFX!

[JFX]

No, Setup=1 just means the filter is only used for sources that are still setup mode (SystemSetupInProgress=1).

With some luck you can get the missing file logged somewhere in \Windows\Panther.

[click-click]

I am trying to convert a wim to vhd and get the following error  after I had manually applied the wim to the vhd with  dism /apply-image /imagefile:Q:\strelec10Eng.wim /index:1 /applydir:z:\. What does the error mean and can it be fixed?

 

[JFX]

Oh, wanted to improve that error message for years.

You have a WinPE selected as source, that's not supported and doesn't make sense.
Use bootice to create a boot entry for the WIM file.

Edited March 17 by JFX

[click-click]

Do you happen to know the bcdedit commands needed to do this? I'm unsure how to add a PE wim file so it will boot. I have a partition for booting different vhds. Do I update the bcd from there to add the wim?

Edit: OK, got it to work. I was missing the boot.sdi.

 

 

Edited March 18 by click-click

[JFX]

I think that I fixed all MinWin bugs reported. 

 

 

 

Edited April 2 by JFX

[Antonino]

My dear Jfx, I have just checked with reboot.pro, and ... after so many problems with the website software update, they seem to wanna "start the ball rolling back again". the only thing of it is they want some contribution on our part, which can amount to just €10 per head, if there are as many of us as are needed to cover the expense. the greater our number, the lesser our contribution. since we have worked on wimbooting for years, we would like to still have your sense for synthesis and poignancy which has stood us in good stead for so long. As I and a few others are of the opinion that minwinning is not just a curiosity, but it can also be used for ordinary activity, it would be wonderful to join our knowledge and experience for keeping vhd's so small and still self-sufficient. To do so, I suggest that we should keep a neat modular linux-like database listing which services and dlls are needed for which various apps to still work in our minwinned vhd's.

Considering my windows-reducing efforts so far, I started a decade ago with a vision from a discovery of file and folder junctions, trying to limit vhd content to just the files and folders needed to reach the desktop interface. all other files and folders I moved outside the vhd, junctioned it all back in and went on like this for years, until I discovered reboot.pro and met Wimb the Flying Dutchman. He briefed me into stopping junctioning files and folders out and back in again, as he had already envisaged a procedure called wimbooting, whereby the wim pointed to a vhd full of pointers that would guarantee the full funcioning of the system, pretty much the same as I was doing with junction, only a lot cleaner and more sensible.

Then the rest has seen us all engaged in trying to reduce vhd more and more until u have come up with your knowledgeable brute-force-assisted minwin that we use today. 

As I was saying earlier, I have never relinquished using minwinned vhd's ordinarily, customizing my system to my advantage and liking before reducing it. the reduction has not always been so spick&span, so to speak, and I had to see what was to be retained in order for my favorite software to keep working. I have also reused my junctions on those components that not every vhd user shares with me (net framework all installed and junctioned out and back into c:\, and the same goes for my nvidia driver which can stay out of the vhd with its 1.7gigs of stuff - no reason to keep it on c:\).

If we just could detect, single out and record what we have found out of services and dlls as to the functions typical of each of them, we could seriously think of using reduced vhd's to full capacity. Don't you think?

Edited March 19 by Antonino

[JFX]

MinWin and RAM booting Windows was a - just for fun - project for me.
I don't share your passion about it. So if you want to create a database, be the first one adding something to it.

For me, I only provide the tool and a basic example.

[suxichao]

On 3/10/2024 at 7:30 PM, wuliyen said:

I need to keep all the files in WinSxS, after deleting WinSxS.ini I get an error!

 

I also encountered the same problem. I want to keep all the files under Windows\WinSxS, but I will report an error 0xC0000005 after deleting WinSxS.ini...

[JFX]

That should be fixed with WimHost.exe 1.1.0.3, posted yesterday.

[suxichao]

23 minutes ago, JFX said:

That should be fixed with WimHost.exe 1.1.0.3, posted yesterday.

I have also tried to use the wimhost that comes with WinNTSetup534, and I have also tried wimhost1.1.0.3. There will be an error after deleting the winsxs.ini (or when the content in the winsxs.ini is empty). I don't know what to do.

Edited March 19 by suxichao

[wuliyen]

minwin Windows11_23H2_22631.3296_X64
An error occurred during the installation of the system.
Could not load DLL C:\Windows\system32\msdtcprx.dll; 
The fact that the file msdtcprx.dll exists!
What is the problem?

SYSPRP ActionPlatform::LaunchModule: Successfully executed 'CryptoSysPrep_Specialize' from C:\Windows\system32\capisp.dll
SYSPRP SysprepSession::ExecuteInternal: Skipping offline-capable module of Microsoft-Windows-Sysprep-SpBcd when running online
SYSPRP ActionPlatform::LaunchModule: Executing method 'Sysprep_Online_Specialize_Bcd' from C:\Windows\System32\spbcd.dll
SYSPRP GeneralizeBcdStore: Found the memory tester object.
SYSPRP SpecializeBcdStore: Found the resume object {5fe9d0f0-e5ff-11ee-8bee-000c29fd7075} for the OS loader.
SYSPRP SpecializeBcdStore: Successfully specialized {9dea862c-5cdd-4e70-acc1-f32b344d4795} application device. Status = [0x0]
SYSPRP SpecializeBcdStore: Successfully specialized {b2721d73-1db4-4c62-bf78-c548a880142d} application device. Status = [0x0]
SYSPRP SpecializeBcdStore: Successfully specialized {fa926493-6f1c-4193-a414-58f0b2456d1e} application device. Status = [0x0]
SYSPRP SpecializeBcdStore: Successfully set the {fa926493-6f1c-4193-a414-58f0b2456d1e} OS device to the boot partition. Status = [0x0]
SYSPRP SpecializeBcdStore: The /detecthal switch could not be removed because it was not found.
SYSPRP SpecializeBcdStore: Successfully specialized {5fe9d0f0-e5ff-11ee-8bee-000c29fd7075} application device. Status = [0x0]
SYSPRP SpecializeBcdStore: Successfully set the {5fe9d0f0-e5ff-11ee-8bee-000c29fd7075} hiberfile device to the boot partition. Status = [0x0]
SYSPRP Sysprep_Specialize_Bcd: Successfully specialized the bcd store. Status=[0x0]
SYSPRP ActionPlatform::LaunchModule: Successfully executed 'Sysprep_Online_Specialize_Bcd' from C:\Windows\System32\spbcd.dll
SYSPRP SysprepSession::ExecuteInternal: Skipping offline-capable module of Microsoft-Windows-COM-DTC-Runtime when running online
SYSPRP ActionPlatform::LaunchModule: Could not load DLL C:\Windows\system32\msdtcprx.dll; dwRet = 0x7e[gle=0x0000007e]
SYSPRP SysprepSession::ExecuteAction: Failed during sysprepModule operation; dwRet = 0x7e[gle=0x0000007e]
SYSPRP SysprepSession::ExecuteInternal: Error in executing action for Microsoft-Windows-COM-DTC-Runtime; dwRet = 0x7e[gle=0x0000007e]
SYSPRP SysprepSession::Execute: Error in executing actions from C:\Windows\System32\Sysprep\ActionFiles\Specialize.xml; dwRet = 0x7e
SYSPRP SysprepSession::Execute: Sysprep mode was not specified, deleting it from registry
SYSPRP RunPlatformActions:Failed while executing Sysprep session actions; dwRet = 0x7e
SYSPRP Callback_Specialize: Internal Providers Specialized Failed. System can't proceed to handle Internal Providers
SYSPRP Callback_Specialize: Specialize return: [126]
SYSPRP Callback_Specialize: An error occurred while either deciding if we need to specialize or while specializing; dwRet = 0x7e[gle=0x00000002]
IBSLIB PublishMessage: Publishing message [Windows 安装程序无法将 Windows 配置为在此计算机的硬件上运行。]
 

 

Edited March 20 by wuliyen

[JFX]

I don't get that error. Make sure you don't miss any dependency of this proxy dll.

[wuliyen]

46 minutes ago, JFX said:

I don't get that error. Make sure you don't miss any dependency of this proxy dll.

Thanks, I'll troubleshoot the possible issues!