I had the same type of errors until I manually created those folders... I am still very green with this but it did work for me once I did that
Ok thanks I have Kb2496290 and KB2496290-v2, in the SoLoR's repo, there are two. So I can removed KB2496290 or not?
I am using the KUC on a newly integrated image and MSU showed no updates but the KUC has quite a few items to address so I will ask a few questions: 1) It shows KB2603229 missing but the setup log shows it installed Windows update "Update for Windows (KB2603229)" was successfully installed. (Command line: ""C:\Windows\system32\wusa.exe" "D:\Apps\229x64\229x64.msu" /quiet /norestart ") 2) I didn't check the AMD Core Parking and yet it shows KB2645594 missing There a few more questions but this is a start... thanks
2645594 does not disable AMD core parking, that's a rumour. If you install it, it will not disable AMD core parking on a PC with a Buldozer cpu. It's a normal power management update. It's just a necessary but not sufficient component for the "disable AMD core parking". What does that meen? All users can install 2645594 without any harm. If you do not have an amd buldozer; no problem install 2646060. If you have an amd buldozzer; you must decide whether to install or not (and if installed no way back!). So the "disable AMD Core Parking" hotfix is only 2646060. With the commandline above only the GDR version of update 2603229 will be installed. And if you look in the output of KUC (packages_out.txt), you will see, that there are 2 lines for 2603229 one LDR 'BF_2603229' and one GDR '2603229' . To install the LDR version use KUC's commandlets. Nevertheless pm me your packages.txt file and a screen shot of the options you select; i will check them.
KB2496290-v2: usbstor.inf, 6.1.7601.17684/6.1.7601.21810 KB2496290: usbstor.inf, 6.1.7601.21642 (LDR) Thanks
GREAT info about 2645594/2646060 and your absolutely correct about 2603229 which make sense since I install it as a silent runonce along with a few others
@McRip, Note that KB2685909 requires Remote Server Administration Tools (RSAT) to be installed otherwise it wont integrate/install. Also I think it would be better to move KB2679255-v2 to SatisfyWU folder since it is obsoleted however WU will nag you about it if it is not installed.
@komm, KB2645594 & KB2646060 does not disable AMD core parking by default, instead it will add the option to disable it to add/remove windows features and it can be disabled/enabled from there.
disablecp.exe in in the root of the msu not inside the cab. So it could make a difference if you only install the cab or if you install the msu.
I saw it now. The difference is disablecp will get execute if installing on a live system however it will not get executed when integrating to an offline image. I am curious to know what it does. Anyway I think we can come to the following conclusion: 1 - KB2645594 by itself does not disable core parking however it updates Microsoft-Windows-UserPowerManagement component to allow disabling/enabling of core parking feature. 2 - KB2646060v3 takes advantage of the updated PowerManagement component by adding the necessary registry keys to the system to disable core parking feature. So in my opinion it is safe to install KB2645594 in any system since we get updated PowerManagement component. As for KB2646060v3 it is best not to install it however if it is installed still we are able to modify the following registry key to disable/enable the core parking feature : HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power CoreParkingDisabled (DWORD) 1 = Core parking disabled 0 = Core parking enabled
SOLOR is very busy and will not update his repository anymore (for the time being). You might want to consider using McRip's repository like the rest of us. As for a script to force LDR installation you can use Installer for Windows Updates by burfadel. However it only works on a live system, for integration you need to modify the script to support offline integration.
it's true!! I talk about updates to more than 1 year, Solor was still avalaible for the updates, I believe must look at what updates I talk if anyone can answer, why KUC detects updates superseded while person (update put on the repo last year) has informed that they were superseded
Ok I think I know what your problem is. You are keeping LDR only hotfix A to force LDR installation of GDR/LDR hotfix B. KUC detects the superseded hotfix A however you need to keep it to force LDR installation. Instead of doing this use integration script to force LDR integration without the need for keeping superseded LDR only hotfixes. An example of such script is installer for windows update by Burfadel or install.cmd in McRip's repo. You need to modify the script to allow offline integration as they are meant for online installations. As an alternative you can use RT7Lite which support LDR integration as well however in my opinion nothing can beat a well written script.
that's right KUC detects updates LDR, superseded by updates GDR/LDR If I removed the updates LDR, at installing it will be a GDR version (not LDR) without script It is obligatory, force the installation LDR, if I want to remove superseded updates detected by KUC, right? And if I will integrate the updates without forcing the installation "LDR," I must keep the updates detected as "superseded" by KUC? Is there a script that forces the installation LDR (if available) and if not available it installs GDR version (for integrate, too)? I do not want to have two times the same updates (those listed "BF") I don't know if rt7lite do that Thanks a lot