Windows 8.1 Hotfix Repository

For the update October Security Release ISO, are able to automatically detect and install?

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

We're going to go through the same fiasco with .net4.5.3 when this visual studio 14 gets released.
I guess most people don't think about it because it doesn't nag for 4.5.2 yet on WU.

 

You need to login to view this posts content.

 

would be good if kuc could remember custom paths to wu & repo, i don't keep mine in the c:\ root. it never remembers.

 

Komm's very clear on that in his help files you have to use cmd line switches:

OFFLINE TO MOUNTED IMAGE

<path to UpdateChecker.exe> /DVD-image-dir:<path to offline image> /up-dir:<path to KUC folder (usually has UpdateChecker.exe in it)> /repo-dir:<path to update folder>

ONLINE TO LIVE SYSTEM

<path to UpdateChecker.exe> /up-dir:<path to KUC folder>(usually has UpdateChecker.exe in it)> /repo-dir:<path to update folder>

I just save my cmd lines in a txt file and re-execute as required by copying the relevant cmd line from the txt file and pasting it into the cmd prompt.

My cmd lines for reference:

Code:

OFFLINE TO IMAGE

E:\KUC_Win8.1\KUC W8.1 UpdateChecker.exe /OnlyCabs /DVD-image-dir:E:\offline /up-dir:E:\KUC_Win8.1 /repo-dir:E:\KUC_Win8.1_Update_1_Repo

ONLINE TO LIVE SYSTEM

E:\KUC_Win8.1\KUC W8.1 UpdateChecker.exe /OnlyCabs /up-dir:E:\KUC_Win8.1 /repo-dir:E:\KUC_Win8.1_Update_1_Repo

ONLINE TO VHD

E:\KUC_Win8.1\KUC W8.1 UpdateChecker.exe /OnlyCabs /VHD-drive:G:\ /up-dir:E:\KUC_Win8.1 /repo-dir:E:\KUC_Win8.1_Update_1_Repo

 

You need to login to view this posts content.

 

not sure if someone noticed, but just integrated all updates and hotfixes in a windows image and after a test installation in a virtual machine, i ran the /ResetBase and while it kept only the latest versions of the files in GDR branch, the ones in LDR branch, still kept all versions of the files
i saw this for amd64_netfx4-aspnet_wp_exe, it kept latest GDR version and all LDR versions, like 3 of them ... and noticed this with other components of netfx4 too considering all hotfixes are LDR only
if not, it may be just my integration that failed and did something wrong

 

This is normal behavior by design, DISM consider hotfixes as high-level packages and skip them (not even checked)

Code:

CBS    Skipping package [Package_for_KB2996566~31bf3856ad364e35~x86~~6.3.1.0] since it has a release-type [Hotfix] that makes it not superseded

 

Just noticed a BuildLabEx change from 17238 to 17328 after this months updates ..

 

ah, cheers, never looked at the help doc

 

You need to login to view this posts content.

 

Regarding the new ESD releases, there are some included updates that have newer versions than the public one (thanks to PointZero for noticing):

Code:

KB2931358: 6.3.1.2 # public 6.3.1.1
KB2931366: 6.3.1.4 # public 6.3.1.3
KB2959626: 6.3.3.0 # public 6.3.2.0
KB2993651: 6.3.1.2 # public 6.3.1.0

however, after looking into each update contents (thanks to SuperBubble's SxS Package Extractor script), the new version are technically pseudo

for KB2993651 and KB2959626:
the components, binaries and manifests are still the same exactly (hash match)
only the package has new version

for KB2931358 and KB2931366:
GDR branch contents are still the same (same situation as above)
LDR have newer component version (20545 vs 20543), but binaries are still the same
so it's just a pseudo version (like Paint ldr hotfix KB999994)

just wanted to clarify this so no one gets confused
maybe they did this to identify the new ESD's upgraded systems or something

 

Could you post these new version updates?

 

You need to login to view this posts content.

 

Currently no, but KB2959626 and KB2993651 can be constructed
KB2931358 and KB2931366 cannot be because they are multilingual, and LDR isn't used or exist in newest image

 

You need to login to view this posts content.