alacran

@wimb I assume you are running WinNTSetup_x64.exe, it uses WinNTSetup\Tools\x64\wimgapi.dll version 10.018362.1. And WinNTSetup_x86.exe still uses WinNTSetup\Tools\x86\wimgapi.dll version 10.015063.0 You may try using WinNTSetup_x64.exe with wimgapi.dll x64 v10.015063.0, version used on older WinNTSetup (x64 & x86), since other versions were buggy, use GetWaikTools to download it. EDIT: Also we need to remember there has been a change in certificate driver enforcement requiring only SHA2 (since Windows 10, version 1803) and the wimgapi version in use may or may not be able to support SHA1, SHA2 or both. wimgapi.dll version 10.015063.0 (15063= v1703) from the table on previous link 10 v1703 supports SHA1 and also SHA2. alacran

To have all drivers available (not as pointers) and avoid troubles when using wimboot mode it is good to add this line \Windows\System32\drivers\*.sys under [PrepopulateList] to your custom WimBootCompress.ini used for capture. (I'm assuming this was done) When you capture an install in wimboot mode using wimlib and use a custom WimBootCompress.ini, the internal Windows\System32\WimBootCompress.ini file is replaced by the custom file used during capture, then latter it is used during applying it in Wimboot mode. wimlib works fine doing so from wimb reports and in my own experience. It seems to me for some reason when using on WinNTSetup wimgapi + WimBoot this is not following this procedure and it is using maybe the file list on WinNTSetup\Tools\WimBootCompress.ini, then as a result having pointers to the required drivers in this case, or perhaps wimgapi do not use the WimBootCompress.ini file anymore (based on JFX comment). Easy way to verify if there is real extracted files or pointers is open your unmounted VHD with 7zip, go to check some of required driver files and see its compressed size, where 0 = Pointer file to source *.wim, >0 = Real extracted file. Also check size for some of files listed on WinNTSetup\Tools\WimBootCompress.ini and then you will have enought info to know if your custom list, internal list of WinNTSetup or none are used durig applying the wimboot install. Sorry I can't help any further but I haven't deal with this problem since when making Wimboot VHDs I always prefer to use wimlib for capture and apply them. alacran

@JFX Attached new version of Spanish Translation with some improvements. alacran 2058.7z

& Then why not install Win 10 on VirtualBox? or maybe before doing this, update the video drivers on your (virtual) win 7 install or try selecting a different virtual video card (if available, since I don't remember right now if this is possible on VirtualBox), it is the video card (dedicated or integrated into CPU) who runs/uses by means of its respective drivers OpenGL 3.0 or higher. alacran

Well, I could say there is no news, just bad updates every month, another thing I can say is they are very consintence. IMHO this is caused mainly because they are always trying to introduce new features/changes every month, they need to stop thinking this way and concentrate all efforts and all required time in fixing all that is wrong first, then when having the OS working flawlessly, they can comeback to introduce new features/changes but not before making extensive tests. alacran

@JFX Good work my friend, congratulations, your tool is always geting better on every new version. Attached improved Spanish translation (based on version 4 Beta 5), VHDs descriptions didn't fit on available space on my previous translations. alacran 2058.7z

@JFX Attached Updated Spanish translation to 4.0 B3 alacran Updated Spanish translation.7z

Yes, you are right. This is a good candidate to cause the issue. But I suggest you also check your RAM just to eliminate another potential cause. You can use MemTest86: https://www.memtest86.com/ Download MemTest86 v8.2 Free Edition for UEFI: Image for creating bootable USB Drive on a Windows/Linux/Mac system Download MemTest86 V4.3.7 (OLD RELEASE) free version for Bios: Image for creating bootable USB Drive alacran

As it seems to be hardware related, you better check your memory and mass storage devices. Also if you haven't done it, disable fast boot, it is a potential source of troubles. Good luck alacran

Thanks for your new update, just downloaded and testing it. It was very easy to find Disable Reserved Storage tweak. Only with the idea to let other members find easier the following additions: - Wim Capture option - Hotfix uninstall option - Driver Export/Import option After a left click on Icon located on upper left corner of GUI you can find them on Offline Windows. alacran

Check your graphic card properties and that will tell you what display resolutions are supported for the graphic card.

Disable Mcafee and try to send an attachment, if it works fine that way, then Mcafee was causing the issue.

@ JFX Thanks very much for your very fast answer, just wanted to be sure before commet mistakes.

@ JFX I have used before the option for add drivers, but not for unsigned drivers, and I have some questions: AFAIK: The procedure should be select + Drivers (Bottom left corner) making right click to allow install unsigned drivers, and the path to the drivers folder. 1 - Is this all? I allready did this and made a WinNTSetup.ini to take a look and I can find Drivers= The path to Drivers folder, but I can't find anything about allow install unsigned drivers. 2 - How can I verify this option is selected? I'm assuming using this option is like ForceUnsigned on Dism. 3 - Is this right? 4 - Wath OSs (and arch.) can use the option for install unsigned drivers? 5 - Does this also modify the BCD to allow Test Mode and/or No integrity checks, or not?

Well what I answered is the safer way to deal with this, but if you want you may try and install the updates after 3/18 one by one and see the results by yourself. But be aware you will find troubles.

See: https://www.ghacks.net/2018/06/21/windows-7-support-dropped-for-cpus-without-sse2/ There they mention The troubles started with March 2018 Security Updates, so you may assume any update made before March 2018 should be safe for a non-SSE2 processor. On the other hand as updates are cumulative now, and there is not a fix for that issue, to be on the safe side I suggest DO NOT install any update made on March 2018 or latter.

@JFX Thanks very much for the info, it will be very usefull. alacran

@JFX I assume it is a command tool, would you please explain me how to use it. Thanks in advance alacran

Hi JFX: I think I saw a single file download for "Recompress Compact OS" for 7 and 8.x, some time ago, but I can't find it, maybe it was lost during server crash, do you still have it? alacran

After seen Biostar Mother Boards (Intel chipset) with this capavility, only thing I can say is Biostar came late to the party, see my post: https://msfn.org/board/topic/177964-windows-7-on-a-coffee-lake-pc/ On it there is a link about an article from August 9th 2018, about new H310 ChipSets supporting Win7 on Coffee Lake platform alacran

@Roffen Go to the page of your PC manufacturer, find your model and check what drivers they have available for each OS, this way you will see what OSs can be installed on that machine. But just to make things a little better, without installing another OS, Download and install Classic Shell 4.3.1: http://www.classicshell.net/ Also this commands (run them as admin) may be usefull for you (valid from 7 to 10), see attached 7zip file. alacran Usefull commands.7z

I always have used for more than 20 years the white "Pelikan" erasers or similars, they do not make excessive wear on golden pins, the idea is to remove the patina and let them almost shiny again. This eraser do not last very long (as it is soft) but I prefer to spend the eraser and not the golden coating on pins. About changing the PSU, it is not a bad idea, and not an expensive one. alacran

First make sure to clean with a soft eraser the golden pins of all RAM boards and also clean the RAM receptacles on MB with a brush and latter pressurized air. If this doesn't fix the problem and as you said you have been using that PC since 2009, it is now 10 years old, so my best guess is: there are internal failures on some or all components (MB and RAM), wich are more evident when they are hot. Anyway if you don't find the source of the failure, only final solution is build a new PC, if you as me prefer to install Win7 on your new rig I recommend to see this thread. alacran

The last version is 65, you can find all language versions here I'm using this version on 7x64 and 10x64 without any issue.

@JFX I have made several Wimboot installs (Win 7 & Win 8.1) using diferent levels of compression, depending on CPU performance. All working fine even on VHDs. I know the option Wimboot Compact: NONE is there since some time ago, Could you please explain me what is the use of these option? As far as I understand it is a Wimboot install without compression, so far good, but what is the benefit in making a Wimboot install then? I never think about its use before and maybe I am not using a good feature of your great tool. alacran