DISM log I really need someone to answer this. I try to slipstream all the required updates for Sept into a mounted image and I get error 0x800f081e blah, blah, not applicable to this image, check DISM log for details.. (2 updates not applicable) Why those updates cannot be named is f*****g beyond me, but, anyways... I check the log and there is no 0x800f081e in it. I search "not applicable" and 2 entries show, but, the only KB's anywhere near these "not applicable" lines show as fully "install pending" in the packages output file. Where, then, do I find the KB's that are not applicable in this DISM log? All the updates I am slipstreaming installed online no problem. Now, I've tried google and get just about everything except what I need. Anybody pretty please.
For proper result you must use the same method as MS does - the machine - real or virtual - that has ONLY ONE hard drive; no logical partitions nor optical disk drives. Install Windows from pen flash drive (must be removed on first reboot) or from WinPE with apply script.
Here it is and many thanks!! UPDATE: got one of them; KB2883457-for Windows 7...not even listed in the DISM log, how convenient plus I have no ider how that KB got in my saved repo. UPDATE 2: second and last one is KB2982037...again not even listed in the DISM log. So, the error tells you to check the log, you check the log which contains no info on the error when searching by KB number, so, how then is one supposed to use this f******g log to find out which files are causing the errors? I must be using the wrong parameters and, if so, could you please point me to what I should be looking for-I don't speak Martian which is what M$ must be using here. Thanks again abbodi1406
I create my VHD on one of my secondary disks and always install Windows from USB and it is always removed on first reboot. I never had this concern using Windows 7-ever; sysprep/audit ran like clockwork. Further, I am not about to disconnect my 2 secondary HDD and the optical drive to accomodate this complete and utter stupidity to create a VHD on my SSD's which are in RAID0-a completely useless waste of write cycles.
Glad you worked it out as for the log, i couldn't see a single error i think this is not the right log, it only has 4 commands: mount, add KB2989647, add KB2959977, discard note that at some size, windows renames the log to dism.log.bak (or compress is as cab) and start with a newer file
I see; I saved Komm's Update commands and Normal/LDR folders from a time when I used KUC to do the nasty. I now put all the updates/hotfixes etc into the appropriate folder; ie: Normal or LDR, then run Update.cmd. The DISM log generated by Komm's cmd is saved there, but, when I get these "not applicable" errors the KUC generated dism.log.bak is entirely unreadable-loaded completely with Chinese looking characters, no text at all. The newer log contains two small entries that mean and show nothing. So, in my ever present genius I figured the C:\Windows\Logs\DISM\DISM.log would mirror KUC's logs; wrong again. Thanks man, really appreciate the effort. It is just so convenient to reuse Komm's command setup (I use only cabs, no msu's) and I did not realize the windows log is not identical to Komm's utility DISM logs. I'll play with things a little; perhaps if I modify his command not to generate it's own logs then, perhaps, windows logs will be right as rain-live and learn, n'est pa'. Of course it goes without saying Komm's modded cmd's are for my personal use only and never shared with anyone anywhere for any reason.