Thanks Trinket! ,, And also i downloaded that .NET Client 4 latest package from on top... But, it says invalid installer? .NET Framework 4.0.30320 Client x64-x86 silent installer (40mb):
Hmm, that's the first time I heard that. Maybe check the hashes and/or download again and try again. Otherwise, I don't know what would be causing that...
LOL; I almost fell for it too...was going to reply with "we get it here in Canada..." type thing-sly devil ain't he!!!?
That is just as the way MS made this. If you will go through all the files you will actually see that most of them have the '30319' designation, but have increasingly higher build numbers based on that base build number. Only some of the files actually go beyond 30319 version numbers and as high as 31106. But, installing NET4 from MS's official release, and then either installing all subsequent updates and/or integrating them will sport the overall build number of the install at 30320, so that is the version number I stayed with (even though there are higher and lower version numbers among all the files).
The following is a list of hotfixes that presently do not have their respective KB articles. If anyone can shed some light on what these hotfixes actually fix, it would be very helpful for all of us. I would not want to miss out any of these hotfixes if they can provide some minor performance improvement and are relevant to my needs. Thanks. KB2319435 bth.inf KB2459268 usb.inf KB2462374 Windows-WindowsCodec; Windowscodecs.dll 6.1.7601.21624. KB2502789 Windows-FileSystemUtilityLibraries; Ulib.dll, Ifsutil.dll 6.1.7601.21650. KB2504602 Windows Communication Foundation KB2505454 volume.inf KB2510636 Windows-Services-Svchost KB2514307 Windows-MSXML30 KB2519944 Windows-MSMPEG2VDEC
SoLoR any chance you could point out with a new legend category what hotfixes are LDR "placeholders"? Maybe add like a asterisk to the KB........*? For me they are not really needed, I force integrate LDR branch.
Hm... ye one day i need to get to this... its "planed", but for some reason i always find something else to do
Sorry, could you explain what LDR "placeholders" is? Since they are not needed, what would happen if I integrate these LDR "placeholders" into a Windows 7 SP1 image? Thanks for the advice given.
The only function they serve is to force the superseding hotfix to install the LDR branch instead of the default GDR
Hm... dism does not work on mounted images if you put .mum in packagepath... almost all errors out with (for example 2 that dont are KB958488 and KB2524375) : Code: Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7600.16385 Processing 1 of 1 - Adding package Package_for_KB2495786~31bf3856ad364e35~amd64~~6.1.1.0 [===========================59.1%== ] An error occurred - Package_for_KB2495786 Error: 0x800f081f Error: 0x800f081f DISM failed. No operation was performed. For more information, review the log file. i dont get why for example KB2524375 is working and most of others do not... it even install proper BF package: Code: Deployment Image Servicing and Management tool Version: 6.1.7600.16385 Image Version: 6.1.7600.16385 Processing 1 of 1 - Adding package Package_for_KB2524375_BF~31bf3856ad364e35~amd64~~6.1.1.1 [==========================100.0%==========================] The operation completed successfully.
Most updates have the same internal layout of the .msu and contained .cab files. KB958488 doesn't have this (its a .NET framework update, with the internals more like a normal .NET Framework update), update KB943790 which is a feature pack (file management API), KB947821-V10 (more versions likely to come), which is the Windows update store check and correct tool, KB982861 (Internet Explorer 9), and the mentioned KB2524375. All other updates within the internal x-KB(article number)-x.cab file, have the update files (these are named 0, 1, 2, 3 and so on, and renamed when installing), manifest files, catalogue files, .mum files, and the manifest .xml file. KB2524375 does not contain any update files! The update files themselves are actually manifest files. I suspect the reason why it works for KB2524375 is probably due to this reason, there are no files that need to be renamed. The update.mum and update-bf.mum files, I believe, controls the renaming of the update files (0,1,2,3 etc), then allows for the proper package .mum to be used from there. KB943790 on the other hand just has the update files 0,1,2,3 etc, and no catalogue or .mum package files, only the update.mum file. If you try and enter the package. mum file normally, the renaming doesn't take place so you are telling it to put in files that don't exist, at least with the proper names, and hence it fails! Since with KB2524375 no renaming needs to be done, no error
dism comes installed, I just choose to use the one in the WAIK folder You can actually dump pkgmgr and go with dism 100%, the only thing that would change from install on a actual PC to install to a offline folder would be the /image:<path_to_image> and /online It would actually be cooler because dism shows progress bar when its installing the hotfix, it can handle CAB, MSU and MUM files...try this in your script and you will see Code: ::This will install to current install echo Installing LDR version as available %z%dism /online /add-package /packagepath:%temp%\cabtemp\qfeldr\update-bf.mum /packagepath:%temp%\cabtemp\qfeldr\update.mum /norestart ... echo Installing GDR version %z%dism /online /add-package /packagepath:%temp%\cabtemp\qfeldr\update.mum /norestart For integrating the updates the only thing you would have to change is /online to /image:<path_to_folder>
well this is pretty similiar to what i have (copy/past procedure to integrate them) and it errors out Code: IF NOT EXIST "%TEMP%\updates.x64" MKDIR "%TEMP%\updates.x64" IF NOT EXIST "%TEMP%\updates.x64\0" MKDIR "%TEMP%\updates.x64\0" IF NOT EXIST "%TEMP%\updates.x64\0\unpacked" MKDIR "%TEMP%\updates.x64\0\unpacked" "%~dp0bin\7z.exe" x -o%TEMP%\updates.x64\0 -i!Windows6.1*.cab "%~dp0updates.x64\*.msu" "%~dp0bin\7z.exe" x -o%TEMP%\updates.x64\0\unpacked\* %TEMP%\updates.x64\0\*.cab FOR /F "tokens=*" %%D IN ('DIR /B /A:D "%TEMP%\updates.x64\0\unpacked"') DO ( IF EXIST "%TEMP%\updates.x64\0\unpacked\%%D\update-bf.mum" ( dism /Image:"%TEMP%\MOUNT" /LogPath:"%~dp0%dism_log%" /Add-Package /PackagePath:"%TEMP%\updates.x64\0\unpacked\%%D\update-bf.mum" ) ELSE ( dism /Image:"%TEMP%\MOUNT" /LogPath:"%~dp0%dism_log%" /Add-Package /PackagePath:"%TEMP%\updates.x64\0\unpacked\%%D\update.mum" ) ) only difference is if there is update-bf.mum i only try to integrate that one... hmz... ill try more later.