RicaNeaga

Hi Rick,
 
TNX for the update!
 
Starting the package dotNetFx452_Full_LDR_x86_x64intl_Slim.exe /y files are extracted and then following error
 
Thiersee
 
Edit:
without switch works!

It was a mistake in update list (the hotfix is not set to be extracted of exe file)
fixed, sorry about that
 
redownload it or extract it manually

I had a similar problem with other KB's I can't remember now. I remember the lack of the date. I wanted to look in the package than I saw the problem.
The problem is that is a .msu in a .msu package. I don't know why it comes like that. Extract it a and should be fine.

I'll have to fix after I've gone shopping. Starving!

Fixed.

haha thanks. It's programming so I'm definitely confident about that exam. Even if it is C++

Info: Microsoft Visual C++ 2005/2008/2010/2012/2013/2014/2015, Microsoft Visual F# 2.0, Microsoft Visual J# 2.0 redistributable packages (with setup junk removed.) Also includes "extra" Visual Basic and C runtimes (see list bellow)

Same as above but excludes F# & J# runtimes
 

Info: Microsoft Visual C++ 2005/2008/2010/2012/2013 redistributable packages (with setup junk removed.) Also includes "extra" Visual Basic and C runtimes (see list bellow)
Some tools and resources for (re)creating your own installer
 
Visual AIO SFX Maker v6 (installer repacker):http://adf.ly/1713566/visualsfxSilent "No GUI" SFX alternative v4:http://adf.ly/1713566/visualsfxngKB2538242 MST Windows Update fix v1.7:http://adf.ly/1713566/wufix5mstKB2538243 MST Windows Update fix v3:http://adf.ly/1713566/wufix8mstMsiTran.Exe -a <transform>.MST <installer>.MSI:http://adf.ly/1713566/msitranSlim down your vcredist 2005/2008 installers:http://adf.ly/1713566/msislim"Extra" Visual Basic/C runtimes installer sourceshttp://adf.ly/1713566/vbcsourceIf you cant find a hotfix try using the KB number w/ this URLhttp://support2.microsoft.com/hotfix/KBHotfix.aspx?kbnum=1234567 Hotfix list
 
 
 
Also includes:
 
 
name version/*-- Microsoft Visual Basic Runtimes -----------------------------------*/ comct232.ocx 6.0.98.39comct332.ocx 6.7.0.9839comctl32.ocx 6.0.98.39comdlg32.ocx 6.1.98.41dblist32.ocx 6.1.98.39mci32.ocx 6.1.98.39mscomct2.ocx 6.1.98.39mscomctl.ocx 6.1.98.39mscomm32.ocx 6.1.98.39msdatgrd.ocx 6.1.98.39msdatlst.ocx 6.1.98.39msflxgrd.ocx 6.1.98.39mshflxgd.ocx 6.1.98.39msinet.ocx 6.1.98.39msmask32.ocx 6.1.98.39msstdfmt.dll 6.1.98.39msstkprp.dll 6.1.98.39mswinsck.ocx 6.1.98.39 picclp32.ocx 6.1.98.39richtx32.ocx 6.1.98.39sysinfo.ocx 6.1.98.39tabctl32.ocx 6.1.98.39vb40032.dll 4.0.29.22/*-- Microsoft Visual Basic Runtimes (16bit) ----------------------------*/vb40016.dll 4.0.24.22vbrun100.dll <none>vbrun200.dll 2.0.9.8vbrun300.dll 3.0.5.38/*-- Microsoft Visual Basic Virtual Machine -----------------------------*/msvbvm50.dll 5.2.82.44/*-- Microsoft Visual C Runtimes ----------------------------------------*/atl70.dll 7.0.9975.0atl71.dll 7.10.6119.0mfc70.dll 7.0.9975.0mfc70chs.dll 7.0.9975.0mfc70cht.dll 7.0.9975.0mfc70deu.dll 7.0.9975.0mfc70enu.dll 7.0.9975.0mfc70esp.dll 7.0.9975.0mfc70fra.dll 7.0.9975.0mfc70ita.dll 7.0.9975.0mfc70jpn.dll 7.0.9975.0mfc70kor.dll 7.0.9975.0mfc70u.dll 7.0.9975.0mfc71.dll 7.10.6119.0mfc71chs.dll 7.10.6119.0mfc71cht.dll 7.10.6119.0mfc71deu.dll 7.10.6119.0mfc71enu.dll 7.10.6119.0mfc71esp.dll 7.10.6119.0mfc71fra.dll 7.10.6119.0mfc71ita.dll 7.10.6119.0mfc71jpn.dll 7.10.6119.0mfc71kor.dll 7.10.6119.0mfc71u.dll 7.10.6119.0msvci70.dll 7.0.9955.0msvcp70.dll 7.0.9466.0msvcp71.dll 7.10.6052.0msvcr70.dll 7.0.9981.0msvcr71.dll 7.10.7031.4msvcrt10.dll <none>  

Not to mention all the weed you smoked in Amsterdam is probably making you think your internets is "funny" (when its not)

The updates may show if you use the (NON Slim) INTL Repack, I have not updated this with Rollup, but I have updated the English
Edit: just had a look inside Rollup MSI and you can see both updates are already integrated http://imageshack.us/a/img577/2152/zh2o.png

Probably you already know about them... 2898869 & 2901126

I don't think there's a bug here.
 
1. I requested that - see here. So really no bug. Some updates are not integratable / better if they're installed during first logon.
 
2. KB976002 is not really an update, but an app. It appears only for EU users, and offers them browser choice / alternatives to Internet Explorer. My suggestion is to remove it from your integration folder / queue, and hide it after windows install in Windows Update

Done.

Just being Devil's advocate ...
 
It seems to me that if integrating certain updates cause some users problems, but other user's are able to integrate them with no problems at all, such as Thiersee, wela, and mooms - all users with experience so I completely believe their results, then, no disrespect intended at all RicaNeaga, I have to agree that the problems with those updates are related to other integrated KBs, or at least an interaction between them. While I understand your logic that if they are causing anyone any problems that we can just move them to runonce where they won't cause anyone any difficulties, and it does seem a more fail safe solution, it would be ideal if that move only occurred if whatever causes the interactions was also included, if we can figure out what that is.

Cheers and Regards

i had many issues with final image - OS installation failed everytime, because some of the updates caused errors - i lost more than 2 weeks on trying to locate "bad" updates.
So I totaly support RicaNiaga and bphlpt last message.
No problems during integration does not garantee successfull installation at all.

@ Rica: this is the image I was testing on and it should work as it is original Microsoft image and as you can see the other languages integrated fine, the problem was the English pack.
 
In romanian answer: Salut. Nu cred ca e vreun avantaj intr-un sens sau altul. Pur si simplu am la dispozitie o imagine si adaug orice pachet de limba de care cred ca o sa am nevoie. Nu ar trebui sa fie nici o eroare pentru ca poti efectiv sa inlocuiesti limba din imagine adaugand una care o vrei si stergand prima limba cu care a venit imaginea. Asa a gandit Microsoft. Probabil ca la origine e imaginea en-us pe care Microsoft a convertit-o in toate limbile individual insa a lansat si limbile separat. pentru instalare ulterioara. Avand in vedere ca pot fi integrate in imagine ca si actualizare e un bonus. Bineinteles ca asta mai ocupa si spatiu dupa instalare pentru ca le ai la dispozitie si le poti schimba din control panel (doar la Ultimate) ca la un telefon, dar baniuesc ca stii deja asta. Eu am nevoie de cateva limbi pentru ca am mai multe cerinte: un frate in Germania, o sora in Austria, mama unguroaica, un prieten in Italia care toti la rândul lor mai au prieteni daca ma intelegi...
 
 
 
@ Lego: I didn't tested the install, just what I saw in the integrated list but as I said it just quicly goes to save the image. Don't know if it has the time to actual integrate the language comparing the time that it spends on the English pack to the other languages that it integrates.
 
Yes, as it shows the other languages it should show the English too on the integrated.
 
I'll wait for a test build with this fixed and i'll test it again with the install in VM too.

@RN, I would think it is just a case of timing and interaction between some of the runtimes, which includes .NET, and some of the other RunOnce items which depend on them being in place.  It is sometimes the installer of the app which utilizes the runtime, and sometimes it is the app itself.  Some of the repacked or slimmed  apps, such as some of Rick's, strip out runtimes which the full installers include, which is why runtimes should always be the first RunOnce items installed.  I would also think that this situation can vary based on architecture.  While I suppose that it is possible that there is something in Win Toolkit's RunOnce code that has an architecture related glitch, I would think it is more likely that it is something in MS's installer code or that of the individual apps themselves.  Just my opinion.
 
Cheers and Regards

if (File.Exists(cMain.SysFolder + "\\Dism.exe")) { sDISMFound.Add(cMain.SysFolder + "\\Dism.exe"); } if (!string.IsNullOrEmpty(cOptions.DISMLoc) && File.Exists(cOptions.DISMLoc)) { sDISMFound.Add(cOptions.DISMLoc); } if (cMain.Arc64 && File.Exists(cMain.SysProgFiles + "\\Windows Kits\\8.1\\Assessment and Deployment Kit\\Deployment Tools\\amd64\\DISM\\dism.exe")) { sDISMFound.Add(cMain.SysProgFiles + "\\Windows Kits\\8.1\\Assessment and Deployment Kit\\Deployment Tools\\amd64\\DISM\\dism.exe"); } if (!cMain.Arc64 && File.Exists(cMain.SysProgFiles + "\\Windows Kits\\8.1\\Assessment and Deployment Kit\\Deployment Tools\\x86\\DISM\\dism.exe")) { sDISMFound.Add(cMain.SysProgFiles + "\\Windows Kits\\8.1\\Assessment and Deployment Kit\\Deployment Tools\\x86\\DISM\\dism.exe"); } if (cMain.Arc64 && File.Exists(cMain.SysProgFiles + "\\Windows Kits\\8.0\\Assessment and Deployment Kit\\Deployment Tools\\amd64\\DISM\\dism.exe")) { sDISMFound.Add(cMain.SysProgFiles + "\\Windows Kits\\8.0\\Assessment and Deployment Kit\\Deployment Tools\\amd64\\DISM\\dism.exe"); } if (!cMain.Arc64 && File.Exists(cMain.SysProgFiles + "\\Windows Kits\\8.0\\Assessment and Deployment Kit\\Deployment Tools\\x86\\DISM\\dism.exe")) { sDISMFound.Add(cMain.SysProgFiles + "\\Windows Kits\\8.0\\Assessment and Deployment Kit\\Deployment Tools\\x86\\DISM\\dism.exe"); } if (File.Exists(cMain.SysProgFiles + " (x86)\\Windows Kits\\8.1\\Assessment and Deployment Kit\\Deployment Tools\\amd64\\DISM\\dism.exe")) { sDISMFound.Add(cMain.SysProgFiles + " (x86)\\Windows Kits\\8.1\\Assessment and Deployment Kit\\Deployment Tools\\amd64\\DISM\\dism.exe"); } if (File.Exists(cMain.SysProgFiles + " (x86)\\Windows Kits\\8.0\\Assessment and Deployment Kit\\Deployment Tools\\amd64\\DISM\\dism.exe")) { sDISMFound.Add(cMain.SysProgFiles + " (x86)\\Windows Kits\\8.0\\Assessment and Deployment Kit\\Deployment Tools\\amd64\\DISM\\dism.exe"); } if (File.Exists(cMain.SysProgFiles + "\\Windows AIK\\Tools\\Servicing\\Dism.exe")) { sDISMFound.Add(cMain.SysProgFiles + "\\Windows AIK\\Tools\\Servicing\\Dism.exe"); } if (cMain.Arc64 && File.Exists(cMain.SysProgFiles + "\\Windows AIK\\Tools\\amd64\\Servicing\\Dism.exe")) { sDISMFound.Add(cMain.SysProgFiles + "\\Windows AIK\\Tools\\amd64\\Servicing\\Dism.exe"); } if (!cMain.Arc64 && File.Exists(cMain.SysProgFiles + "\\Windows AIK\\Tools\\x86\\Servicing\\Dism.exe")) { sDISMFound.Add(cMain.SysProgFiles + "\\Windows AIK\\Tools\\x86\\Servicing\\Dism.exe"); } if (File.Exists(cMain.SysFolder + "\\Win8Dism\\Dism.exe")) { sDISMFound.Add(cMain.SysFolder + "\\Win8Dism\\Dism.exe"); }Was easier for me just to paste in the code lol.

The 'activities' are already administrative permissions.

Note:
 
Not to mention its enormous size, KB947821 should not be used offline at all (integrated or silent install), it's ment only for verifying Online system Updates and Packages

I was asking how the Tools/Downloads menu should be re-arranged, not another redesign LOL.

Looks like this one was also related to a ~ RDP update (or an update that's not 100% recommended to be integrated). See here. So you can close this thread as solved, Lego, after solving my ''ugly'' important request from the liked thread.

Regarding KB943790.
The KB describes it as an update to be applied to winpe.wim, not the main wim. So, it doesn't look like it should be integrated OR silent installed. If anything, it should be integrated to the winpe.wim.

The great thing about the menu stuff is that I can add Gadgets #1, Gadgets #2, etc.. links. So if anyone has any great wallpaper, theme pack links or whatever I can add just let me know.
 
 
I will remove Windows ISOs from Basic and have USB Boot Prep and ISO Maker in basic.

Fixed.