Is it just me or is installing Windows 9x/NT in the latest developer builds problematic?

[BridgeHeadland]

Question

For some reason, it is very advanced to even start an installation of a Windows operating system, more advanced than otherwise, I have even had to install Windows ME from hdd.vhd (Drive C) to itself, or it doesn't work. In some places the installation and/or setup hangs, and in some places the whole thing crashes. I have experienced many hours of nonsense, both with installing to IMG and VHD. Today I have experienced that the copying of the Windows files to hangs up in the tenth percent, when I tried to install Windows ME into a IMG file.

Have you checked that no similar question(s) exist?

• [X] I have searched and didn't find any similar question.

Code of Conduct & Contributing Guidelines

• [X] I agree to follow the code of conduct and the contributing guidelines.

[BridgeHeadland]

Now I don't understand a thing in the world! The Developer Build from June 30, which I downloaded that day, has recently acquired a new behavior. It's like every time I create a new VHD file, it's somehow corrupted. It seems like that every time I try to install Windows ME, both from the ISO file (Drive D (and sometimes E)), and when the files are in the VHD file (Drive C). Is this common with this current developer build?

In these TXT files, you see what my current configuration is set to. dosbox-x.txt dosbox-x.reference.full.txt dosbox-x.reference.txt

[maxpat78]

By the way, this is Windows ME successfully installed and booted (...like many other Windows 9x OSes...) with Windows x64 dev. build 2023.08.11.

I used a Fixed 1 GB VHD just to be sure, and no corruption appears (I refer to #4406).