Yes I integrated it into the installer by adding it to the correct hotfix directory and then running the Applyhotfixes.cmd then I run the .mst to create the .msi files. I did uninstall my build rebooted the machine and then installed your latest release and I still have WU complaining about KB2468871 This is on both a x86 and x64 build running in VirtualBox do you think it could be VB? Thanks, dolivas
I noticed the same thing myself, KB2468871 shows up on WU. Maybe running the applyhotfixes twice resolves this? I thought it might have had something to do with GDR and LDR, and the way these are installed as opposed to the Windows updates.
Hmm... let me check my registry and see if any mention of the KB's remain and install again, if 2 or more experience this I wonder what is going on. I'll report back if I find anything. EDIT: Well, KB2468871 shows up as installed in my registry, but I do indeed see it available in WU but it is classified under "Optional" whereas previous ones showed up under "Important" for me (so I didn't notice this one at first). But yes it does show for me as well. Not sure what to think of it, the reg entries should tell WU this is installed, so I don't think running the 'apply hotfixes' twice could solve that... Could it be a WU glitch again?
Applying those hotfixes twice doesn't work... I just tried it. KB2468871 is still showing up. But when I run that KB manually, it disappears from WU... Weird, this one has never been a problem before?
Running it twice was just a thought Do the actual files installed change from before and after running KB2468871? - I have to rush off in a minute and don't have time to check for myself!
Also you can hide this WU update for .NET 4: Code: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2533523] "ThisVersionInstalled"="Y" "InstallerName"="Windows Installer" "InstallerVersion"="5.00" "PackageName"="Update for Microsoft .NET Framework 4 Client Profile (KB2533523)" "PackageVersion"="1" "Publisher"="Microsoft Corporation" "PublishingGroup"="Developer Division" "ReleaseType"="Update" Btw is there a way to hide normal updates via registry or commandline? Especially it goes on my nerves that im offered the Malicious Software Removal Tool update - every month :s
Not just the hidden updates are stored in there, it has everything, even all the update history...what I would recommend is you stop windows update service, delete edb, restart windows update so that a new edb is created (keeps the size small), hide the updates you dont want, back up the file and add it to your wim (not 100% sure it will work, Windows may want to delete your added one and create a fresh one but its worth a try)
Yes, I did try creating them myself several times and I told you I got the same results. It is no biggie to me, but that doesn't mean I'm going along with the falsehood there I did try and neither mine nor yours worked for me then, at which point you stopped replying to me. Those are the facts. Thanks, I'll try your new icon mst's. KB2468871 still shows up in WU. I tried different order of integration but to no avail. I did notice a V2 of this KB, the article was from Aug 14, so I thought that must be it, but when I unpack the .exe the .msp inside has the same hash as the one I already had... So I don't know what the deal is with KB2468871.
Indeed.I have a new clean install coming at the end of this month.I'll give it a try. Thx for the tip.
Hi ricktendo64, I hope all is well I can not speak for Trinket but I did try and succeeded the problem I found was you are not deleting these in the FeatureComponents Tables Code: F_Installer_IdentityARP Installer_Setup_ddf MSICache_Core_amd64_enu Netfx_NetFxRepair Netfx_SetupUtility It does not matter if I use SoLoR's MSI's if I use the new MST's you just posted the problem is fixed because you removed the invalid entries in the latest MST's There is one other error in the latest MST's if you look in the File Tables scroll down to this entry mscorier_dll_amd64 and also mscorier_dll_x86 you will see it is red where the Language field is because there is a error change it to 1033 for both and the error will be gone. I am not an MSI expert but these are my findings. I am going to try a new build with the files you just posed to see if I still have a problem with KB2468871 do you? Thanks, dolivas
I did not post about deleting these because they were already deleted using my original setup slimmer, I was posting instructions on what further needed to be done to get the icon added This is not an error nor is it caused by the MST's, you can open the regular MSI's and you will see it in red. To view what the "error" is right click it and choose show errors... BTW yes I also have the problem with KB2468871, IDK what MS update is whining about
Thanks for the info and I think that is where the confusion came from I was not reading it as I had to use your original setup slimmer (Oh well all is good now we know what we were doing wrong.) Yes I see the error in the regular MSI but it is still an error not that MS would put out something with an error in it...
In connection with the official release test version windows 8, and updates come from WU, I have a question-sentence: lay out updates for and for him it is not always and not everyone is able to run the WU in the absence of Internet, if possible.
Found the issue with the m folder, its been fixed locally What issue did you have with some updates not installing? with the test4g I added the check for the servicing stack, since I believe that needs to be installed first. If this isn't the main cause and there is another updates that means a successful complete update let met know. Also let me know if you want the updated test4g (made some other minor changes but nothing that warranted another upload).
I can't point out exact updates that were causeing the problems.One was one of the early pre 247xxxx ones and other was in the middle.Something 252xxxx i believe. But this was a local problem (my current install is a little broken already) and not a problem with the script. The script worked fine.Did not try the integration feature yet (is implemented?). Gonna leave this for end of the month when i cook a new ISO for clean install and integrate LDR hotfixes.