Those files are required to complete the pending servicing operations you can get rid of them by running ResetBase operation, after booting the image or else, don't integrate updates that trigger the pending status (i.e. do not enable .NET 3.5)
Integration into boot.wim: Code: dism.exe /image:"c:\mount" /Add-Package /PackagePath:"i:\W10UI_4.1\16299.15_Updates_x86\windows10.0-kb4058043-x86" Deployment Image Servicing and Management tool Version: 10.0.16299.15 Image Version: 10.0.16299.125 Processing 1 of 1 - Adding package Package_for_KB4058043~31bf3856ad364e35~x86~~10.0.1.0 [==========================100.0%==========================] Error: 0x800f081e The specified package is not applicable to this image. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log This "store" is install.wim only
Hey abbodi1406, thanks for responding to my thread Something else to mention is that the folders inside InFlight apparently were all empty from the start. I assumed they were there for a reason (unless empty folders have another meaning?). With the added side-effect/possibility to render "Reset Windows" unusable¿ Oh, i didn't know that Is image cleanup in your W10UI script still recommended (i.e. that it won't break any Windows functions)?
I'll have to test later since my Windows is full of errors (maybe it's caused by the faulty .NET Framework 4.0 I told earlier). Anyway, is it easy to set the .ini file? EDIT: Windows Update detected an update so it means it isn't fully updated in spite of having integrated the mentioned updates.
Which is what i stated Thanks a lot for clearing it all up. btw: Am i correct that Windows has .NET framework 3.5 feature enabled by default? All that remains for me now is applying some default user tweaks to \Users\Default\NTUSER.DAT or HKEY_USERS\.DEFAULT (if there's no difference between them) and hopefully i'm done/ready to run a final test edit: Note to myself. HKEY_USERS\.DEFAULT (or Windows\System32\config\DEFAULT) apparently belongs to LocalSystem and not \Users\Default\NTUSER.DAT.
msu file already contain the executables to remove the drivers you only need the update if you have the affected cards
Windows Update MiniTool didn't detect any updates and which Windows and Office updates should I download and install with WHD (I suppose I only have to install the updates inside the 16299 folder since I have the RS3 but there is also an update inside a RSAT folder which is inside an Extra folder)? I don't have an ISO so should I extract the Office 2016 x64 RAR folder and copy the updates to the updates folder and they will be automatically aplied during install? What if I downloaded some updates for some Office programs that I choose not to install during setup (like Skype and OneDrive for Business, for example) or for some things for Windows 10 that I remove with MSMG ToolKit or NTLite? Will I have my Windows 10 16299 x64 and Office 2016 x64 fully updated if I integrate this updates? EDIT: I downloaded and integrated all the available Office 2016 x64 updates in WHD and Windows Update still detected an update (related to Skype for Business which I didn't even install)! Regarding Windows 10 16299 x64, after I downloaded and integrated all the available 16299 updates Windows Update didn't detect new ones!
Even if you didn't install Skype for Business, WU will detect the corresponding updates. The same applies to Project and Visio.
If you don't know what RSAT or don't need it, then don't downloaded it -- If you installed Office Suite (Pro Plus, Standard), you will get updates for all or most products included, even if you choose not to install some of them because components are shared, and MSI mechanism detect parent suite product codes...
OK, thanks! Well, but I don't need Skype for Business and OneDrive for Business so I shouldn't integrate its updates or install new ones regarding them, right? And what about the fact that Windows Update still detects a new update after integrating all the available Office 2016 16299 x64 updates in WHD?