OK, on a x86 VM install (with IE9) with the list I previously posted, WU offered the following updates: critical: 2658846 (was not in my list) (now added) 2676562 (was not in my list) (now added) 2799494 (was not in my list) (now added) optional: 2670838 (platform update, IE10, etc.) (ignore) 2679255 (was not in my list) (now added) 2786400 (was in my list -- WU, GDR, or manual install needed) So I will add KB2658846, KB2676562, KB2799494, and KB2679255 to my x86 list in earlier post. Again, as with x64, KB2786400 would not via the v27j script so I had to install it via WU instead. KB2488113 (x86) was also 'not applicable', as was the case for x64.
For the WU satisfy updates, the LDR component (the functioning component) is installed, it's just the GDR component which is required to satisfy Windows Update that isn't. Ideally you install as few of these non-active updates as possible. One of the problems of WU determination is that it can vary from system to system depending on previous state of install (that is, fresh system or an install that's 2 years old). List the updates that still show in WU after using the installer and I'll add it to the WU Satisfy list. Like I said though, these updates are installed correctly despite showing in WU
@parapher It's weird you got three kernel related updates - 2679255, 2676562 and 2799494. They're somehow WU satisfy related updates, however I think something went wrong, maybe it was best to re-run KB947821-v26 and try again to check for updates.
I think it's just these, Burfadel: x64: kb2757638 kb2786400 x86: kb2786400 They were present in the folders in which I ran your script, but WU still offered them afterwards.
OK, I'm just capturing the image right now, after which I'll get back into that VM and run the readiness tool
Ok, It's weird that it's good for you with windows 7 and for me, it does not work. You integrate the two hotfixes and you can install Windows 7 in UEFI without problem, then? You can tell me "date" (digital signature) of "Bootmgfw.efi" file in Windows\Boot\EFI Thanks EDIT: you can integrate the two hotfixes with WinToolkit? Even KB2757588? is not really a .cab (But archive), No?
When you add the update to the WU-satisfy list, is that the same as saying that update will then not install in LDR mode? Or is there a way to both get the functional files out of the update (LDR) and still satisfy WU? Even though a satisfied WU can be nice, it would indeed be preferable to have the newest file versions inside an update, rather than having WU behave.
With a WU satisfy update, when both LDR and GDR versions are present the LDR version of the update is still force installed and active, the GDR versions of the WU satisfy update is installed (to satisfy WU) but remains inactive. Basically the installer will install and have active the best version available for each update, as long as that update is applicable (as determined through DISM). The installer can be used with any mix of updates, but of course ideally you use the hotfix repository, in which case all the updates should be applicable. The only times that updates aren't applicable is where they are for a feature that you don't have, such as some server updates. You can remove these by choosing option 4 in the install menu.
i dont know this solution can fix your problem or not .... i think is not the windows UEFI boot problem ,maybe is windows 7 installation UEFI problem 1.extract KB2757588.cab (should have Bootmgfw.efi & Wdsmgfw.efi) 2.in the installation folder copy the efi\microsoft\boot folder up one level into the efi folder as efi\boot 3.select the KB2757588 bootmgfw.efi and rename to bootx64.efi 4.Copy/Move the renamed bootx64.efi file into the efi/boot hope this can help fix your problem .... glad your problem can be solve ...
Thank you but this is what I do and it does not work. Can not boot from the USB key (UEFI) to install Windows 7 If I put the original "bootmgfw.efi" file (included in the ISO), rename to "bootx64.efi" is ok
if want to boot UEFI USB the file system must need FAT32, just file system FAT32 can boot UEFI USB only , other file system is cant work for UEFI USB
@bapt With what app do you make the windows iso after everything is integrated? Suggestion: use Win Toolkit's ISO Maker, with the default options (BIOS and UEFI)
b4 i also have the problem , but the UEFI boot is not work for windows 7 but is work for windows 8 , i also dont know where the problem ... sorry about that my poor IT cant help you ~