@Enthousiast The file I have is this one: Code: File: DirectX_June2010_x64.WA CRC-32: e8b17978 MD5: 78797de2739070bbc6329bc52a75d440 SHA-1: 7244d80c532c882a0a945d9d97e0067dd0b35294 SHA-256: 7e249a75611fb4effa59bd35fce8c7e9de59557f6343e8612411593518861477 SHA-512: 792c12ad95e60b1deac873f217c412f701e8734e3859f6068d39156aa5c835a8bf782c2f5ef15c72d05d0f729604024d9cf98ce89e9072acaea7a62367a7daac
@parafer 13 months ago simplix started using KB3125574-v4 rollup in the updatepack. That replaced a boatload of updates and the updatepack works much faster since then. That's why you see ~50-60 updates in the installed list. Read the OP, you'll find out how to have DirectX 9.0c, .NET Framework 4.8 and Visual C++ runtimes integrated in the windows 7 image.
Thanks for the explanation! Interesting. Since I use sysprep (so install on live OS but in VM) I have an .iso that I load with all my .NET, DirectX, VC Runtimes and some extra runtime installers, and various cleanup scripts and tweaks that I apply in the VM before finalize.
Sorry for me with latest updatepack Integration in a windows 7 enterprise sp1 work , But windows hang on windows 7 startup logo :/ Usb 3.0 ( ported from windows 8.1 ) and nvme ( windows 7 update from microsoft ) hang Whats wrong ?
Does vmware have an option to emulate EFI bios similar to virtualbox? That's the only thing I can think of that could cause this hang.
/NVMe - integrates NVMe support(KB2990941-v3-x86-x64 and KB3087873-v2-x86-x64) into the install.wim and winre.wim switch to exclude nvme update ?
Yes if we use NVME with lsi logic it hangs on post OOBE first login but if we use SCSI with NVME & be sure that we are using PCIE based NVME on host machine then it works . i have tested it by my own to install win7 as guest os via vmware workstation not to use vmware player
I don't maintain the updatepacks, @simplix does, and there is no harm in integrating the 2 nvme support updates from msft. Best would be to stop using win 7 on modern hardware entirely.
If you need windows 7 for old business application , you can virtualize But unable to have up to date using your pack because nvme ( unusable on vmware 14 and 16 ) Unusable on virtualbox , If your pack not working on specific real hardware it's not critical , But on hypervisor .... not depend on real hardware !