Jump to content

Recommended Posts

  • 3 weeks later...

Posted
On 3/6/2022 at 5:12 PM, alacran said:

JFYI

My Mini-10_es-MX.vhd boots very fine now. (Made using Win10_2004_Spanish(Mexico)_x64.iso)

By the way there is a typo in the file name it says: Lanugages.txt not Languages.txt

Any way I edited it to keep all es-ES and es-MX, and saved with both names, your program will use the one it has coded, during you fix the typo.

For use in es-MX version, I did same thing in my modded version of SySWoW.txt that was used in Mini-10-US.vhd to fix LibreOfficePortable issue, and also try to cover other possible cases like that.

Also edited System32-DLL.txt, commenting the following lines:

; \Windows\System32\KBDLA.DLL   >>>   Spanish Latin American KB

; \Windows\System32\KBDSP.DLL   >>>   Spanish KB

; \Windows\System32\SensApi.dll   >>>   Requided to boot notepad++   now it boots and works fine, but fails when trying to save as....

I found Paint can't also save as... but I had same issue before in a wimb's project aand I know the cure for that:

; \Windows\System32\shellstyle.dll   >>>   This is used by Paint to save as...., this very possible will also fix same issue in notepad++ (pending to test, will report back).

 

Adding WlanMM.dll, let me see the available Routers now, but if selecting one, the usuall next dialalog to Connect and type the Password is not shown. Something else is still necessary.

alacran

 

got another link to syswow.txt?

link is down.

  • 1 month later...
Posted (edited)

I have an updated W7 vhd that I boot loacally and I want to now use it in a VM (VBox). Since the BCD for booting was loacated outside of the vhd, I used Winntsetup to redo the BCD as shown below. The problem is, when I use the vhd in a VM, it starts to boot, but BSODs with 7b. When I try safe mode, it also abends. The last entry I see on the console before the BSOD is Classpnp.sys which is a storage class driver. So I assume I have a disk  or controller driver installed in the vhd that doesn't work in a VM which may be causing the crash.

@JFX or anyone else that might know how to resolve this, or something to try, please let me know.

W7BCD.png.78f35198187c5288b7a9403da3af7e2a.png

Edited by click-click
Posted (edited)

I don't think any of these apps will install  drivers for a VM when converting (I've already tried some others). Since I already have a bootable working VHD there is no need for me convert unless there are apps that actually redo the storage drivers to work in a VM which I doubt. Finding the non-compatible driver(s) in the VHD is the problem.

 

6 hours ago, click-click said:

 

 

Edited by click-click
Posted

Did originally.  Forgot as time went on, lol.

If it were me, my next step would be to uninstall your current version of VirtualBox (which I have to assume is "new") and drop down to the 5.x branch.  I'd have to research further, but you want a version that PRE-DATES hardware capabilities like "TPM".

Just a hunch...

Posted

I've never done what you are attempting, I admit, so I am only going by "educated guess".

We use Acronis at work for the task you are attempting.

But it's also one of those things we only need to do once every 18 months or so.

We all forget the process and have to reinvent the wheel every time.

  • 3 weeks later...
Posted
On 12/2/2025 at 9:46 PM, click-click said:

Finding the non-compatible driver(s) in the VHD is the problem.

 

 

FYI: Thw BSOD 07b was caused by the Intel RST driver. I had to add the Standard SATA AHCI Controller driver (mshdc.inf) to the VHD and then do a safe boot to remove the Intel Controller driver. After that, I was able to use the VHD in Vbox.

  • JFX changed the title to WinNTSetup v5.4.2
Posted

WinNTSetup 5.4.2

- fixed could not start minimized
- fixed some wimcapture issues
- fixed possible buffer overflow in some minwin functions
- fixed crash on malformed Win10Builds.ini
- updated ux and drvinst patcher for Win11 build > 28000

Posted

Great to see an update, thanks for your continued support for WinNTSetup.

Last week, I did some tests on the 28000 ADK and installed W11Pro 28000 too, just to see how bad they screwed it up this time.

You're our only hope for removing all the junk (from the Setup, for one thing) and letting us use the basic NT core, which I guess is still OK for now.

Best wishes for the New Year!

Posted (edited)

By the way, build 28000 was not as bad as I had feared, I created an install.wim from UUP, then removed Winre.wim, the size was not too bad (less than 4gb).

And while we're talking about this particular build, here's the reg I applied to stop the TaskManager bug:

(I'm not really interested in newer builds for now, I used build 28000 because I could use some files from install.wim in my ADK PE 28000)

(PS: Also nice to see the "Remove Defender" stuff still seems to work - If anybody knows of recent registry settings needed to "clean" the latest builds, please share!!!)

Windows Registry Editor Version 5.00
# Resolve Task Manager process might continue to run in background after app is closed
# Undo - Delete HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14 Registry Key and restore default values.
# You will need to open CMD as administrator. Type the following command in CMD to Undo:
# REG DELETE "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14" /f

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14]

# KB5067036 CU Main Feature Bundle, Enable Most features. ViVetool ID: 57048231 (CFR RKey: 1318466191)
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14\1318466191]
"EnabledState"=dword:00000002
"EnabledStateOptions"=dword:00000000

# [Task Manager] Fixed: Some apps might unexpectedly not be grouped with their processes (Require 1318466191). ViVetool ID: 49407484 (CFR RKey: 4188347533)
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14\4188347533]
"EnabledState"=dword:00000002
"EnabledStateOptions"=dword:00000000

# Addressing the requirement for a CFR Key in Windows 11 Insider Preview Build 28000 that Task Manager cannot terminate the process using the [X] button. ViVetool ID: 45036792 (CFR RKey: 4027031693)
[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\FeatureManagement\Overrides\14\4027031693]
"EnabledState"=dword:00000002
"EnabledStateOptions"=dword:00000000

 

Edited by Atari800XL

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   0 members

    • No registered users viewing this page.
×
×
  • Create New...