Why is it enterprise but based on ultimate? i asked this before iirc, never got an answer, when it is enterprise based why not require the enterprise ISO instead of the ultimate ISO?
Reuploaded the tool, - Added "Segoe UI Emoji" v1.45 font from Windows 11 - Added MS Edge WebView2 Runtime 109.0.1518.140
Did this occur? My download today, which took 4 hours, downloaded a file named win7platinum_tool_2023-10-10.7z. EDIT: Apparently so, since the above mentioned files are there, but it might have made more sense to re-date the file with today's date. Also, I'll agree with @Enthousiast that since you are supposed to be ending up with the enterprise version, which I agree is the right decision, why not start with an enterprise ISO? Don't get me wrong, I've always used the Ultimate ISO to start with in my previous installs, but there must have been some reason besides "Why not?" for you to start with Ultimate and then switch to Enterprise. Did some tool you used require Ultimate or not function with Enterprise? Just curious.
Like said, the edition shouldn't really matter as long as it's English, SP1, U, Media Refresh, no Office. It's the most "popular" ISO around and thus most available one. It's easier to tell people "use exactly this one which is easy to find" than to list and test everything that is compatible. By checking integrity with a checksum, it's also made sure it's exactly correct and not corrupted or whatever, which the ISO creation tools probably wouldn't catch. The edition is really just a configuration thing. If the release version is the same, the files should be otherwise identical. IIRC it's also possible to change the edition of a live system. It only affects which activation methods can be used and what features are unlocked. You also kinda answered your own question with this: So did everyone else. If someone already has a Windows 7 ISO, it's probably the Ultimate one. So it's the first choice to use as base, simple as that.
Is it possible, or appropriate, to add the Multi-OEM/Retail Project {MRP} - Mk3 to this platinum project?
No, you shouldn't add another activation method, it's already done with KMS. Enterprise isn't an OEM SKU anyway, and as such isn't listed as supported by MRP. That being said, it's of course possible to edit the script, change the edition to something other than Enterprise, remove the KMS parts and use something else instead, but I don't know why anyone would nor should.
If you want to easily test this in a VM and have Vagrant and VirtualBox installed, there is a Vagrant box available by using this Vagrantfile: Spoiler: Vagrantfile Code: # Windows 7 Enterprise x64 # config BOX_CPU_COUNT = "2" # cpu count BOX_RAM_MB = "8192" # RAM in megabytes BOX_HOSTONLY_NET = true # enable host-only network adapter BOX_HOSTONLY_IP = "192.168.56.101" # host-only network adapter ip BOX_USER_NAME = "win7" # admin account name BOX_USER_PASSWORD = "123" # admin account password Vagrant.configure("2") do |config| if Vagrant.has_plugin?("vagrant-vbguest") then config.vbguest.auto_update = false end config.vm.box = "anzz1/win7x64" config.vm.provider "virtualbox" do |vb| vb.customize ["modifyvm", :id, "--ioapic", "on"] vb.customize ["modifyvm", :id, "--memory", BOX_RAM_MB] vb.customize ["modifyvm", :id, "--cpus", BOX_CPU_COUNT] end if BOX_HOSTONLY_NET == true config.vm.network "private_network", ip: BOX_HOSTONLY_IP end config.vm.communicator = "winrm" config.winrm.username = BOX_USER_NAME config.winrm.password = BOX_USER_PASSWORD config.vm.post_up_message = <<-HELLO ============================== CPU Count : #{BOX_CPU_COUNT} RAM (MB) : #{BOX_RAM_MB} SSH Port : 22 => 2222 Telnet Port : 23 => 2223 WinRM Port : 5985 => 55985 RDP Port : 3389 => 33389 Username : #{config.winrm.username} Password : #{config.winrm.password} Host-Only Adapter Enabled : #{BOX_HOSTONLY_NET} IP : #{BOX_HOSTONLY_IP} ------------------------------ Windows 7 Enterprise x64 booted ! HELLO end Then just connect via RDP, WinRM, SSH or Telnet — pick your poison. You can achieve the same result for your own VM by using these tweaks (which are off by default) after installation: "Enable RDP Server", "Enable Telnet Server", "Enable Remote Management", "Enable SSH Server". --- Right, added a couple more options.
That seems strange indeed, the files seem to be missing somehow. I can't say what happened there, I only have some guesses. You mentioned struggling with the laptop and I see you're using W10, so it might be some strange Windows 10 related trouble, or maybe disk corruption? While only the first two of these points should be needed, here's some things to try: 1. Make sure you have enough disk space on the drive the tool is in, at least 20GB 2. Change the power settings to make sure the PC or its' hard drive doesn't go to sleep while working, on a laptop plug it into the wall, and don't use it while it's working 3. Put the tool in a short path without spaces: "C:\WIN7PLATINUM" 4. Run "cmd" as Administrator 5. Disable Windows Defender or any other anti-virus which might be blocking disk access for some unknown reason 6. Try using another PC to create the ISO EDIT: Also, never use Rufus, as it is garbage. If you are making a bootable USB instead of burning a DVD, refer to the "BOOTABLE USB INSTRUCTIONS" in the README on how to do it the official way using official tools.
Updated to 2023-11-15 - Add latest Patch Tuesday updates KB5032000, KB5032252, KB5032383 (20231114) - Update VCRedist to 20231114 - Update .NET Framework 4.8 to 20231114 - Update .NET Framework 3.5/2.0 to 20231114 - Update .NET Core 6 to 6.0.25 - Update .NET Core 7 to 7.0.14 - Add .NET Core 8.0 - Add Roboto font
Very nice. EDIT: @kebabstorm When trying to make a bootable USB from ISO: The USB stick is 16GB, is it not enough?
8GB is enough. Please post the output of your step 1, which are the "diskpart" commands. Either the stick is broken and the "diskpart" formatting part failed somehow, or the flash memory exhausted its' write cycles and isn't writable anymore. Or the USB drive reports a fake size and is not really 16GB, which is known to happen sometimes.