© KEiGHT Posted June 3, 2014 Share Posted June 3, 2014 WinToolkit 1.4.40.1 Microsoft Windows [Version 6.1.7601]Copyright © 2009 Microsoft Corporation. All rights reserved.D:\SOFTWARE\WINTOOLKIT>Set SEE_MASK_NOZONECHECKS=1D:\SOFTWARE\WINTOOLKIT>"C:\Windows\System32\Dism.exe" /Image:"C:\WinToolkit_Mount" /Add-Package /PackagePath:"D:\TEMP\Updatesx64\Updates\Windows7-x64\General\Windows6.1-KB2820331-x64.msu" /ScratchDir:"C:\Windows\Temp\WinToolkit\ScratchDir" /EnglishDeployment Image Servicing and Management toolVersion: 6.1.7600.16385Image Version: 6.1.7600.16385Processing 1 of 1 - D:\TEMP\Updatesx64\Updates\Windows7-x64\General\Windows6.1-KB2820331-x64.msu: An error occurred applying the Unattend.xml file from the .msu package.For more information, review the log file. Error: 0x800f0830Error: 0x800f0830DISM failed. No operation was performed.For more information, review the log file.The DISM log file can be found at C:\Windows\Logs\DISM\dism.logD:\SOFTWARE\WINTOOLKIT>exit ===same thing with KB2819485 An error occurred whilst integrating an update!Exception:Microsoft Windows [Version 6.1.7601]Copyright © 2009 Microsoft Corporation. All rights reserved.D:\SOFTWARE\WINTOOLKIT>Set SEE_MASK_NOZONECHECKS=1D:\SOFTWARE\WINTOOLKIT>"C:\Windows\System32\Dism.exe" /Image:"C:\WinToolkit_Mount" /Add-Package /PackagePath:"D:\TEMP\Updatesx64\Updates\Windows7-x64\Hotfix\Windows6.1-KB2819485-x64.msu" /ScratchDir:"C:\Windows\Temp\WinToolkit\ScratchDir" /EnglishDeployment Image Servicing and Management toolVersion: 6.1.7600.16385Image Version: 6.1.7600.16385Processing 1 of 1 - Adding package D:\TEMP\Updatesx64\Updates\Windows7-x64\Hotfix\Windows6.1-KB2819485-x64.msuD:\TEMP\Updatesx64\Updates\Windows7-x64\Hotfix\Windows6.1-KB2819485-x64.msu: An error occurred applying the Unattend.xml file from the .msu package.For more information, review the log file. Error: 0x80070005Error: 5The specified image is no longer serviceable.Unmount the image and discard your changes. Mount the original image to try the operation again.The DISM log file can be found at C:\Windows\Logs\DISM\dism.logD:\SOFTWARE\WINTOOLKIT>exit----------------------------------Something bad has happened to your image and can no longer be worked on! There was no point in continuing.NOTE: This usually happens when you try and integrate a language pack of some sort without integrating the Windows language pack first.-For example, if you want to integrate a French language pack for Internet Explorer. Then you need to make sure to add the French Windows language pack first!You may also want to try the integration process without including the last update that integrated successfully.Exception:Microsoft Windows [Version 6.1.7601]Copyright © 2009 Microsoft Corporation. All rights reserved.D:\SOFTWARE\WINTOOLKIT>Set SEE_MASK_NOZONECHECKS=1D:\SOFTWARE\WINTOOLKIT>"C:\Windows\System32\Dism.exe" /Image:"C:\WinToolkit_Mount" /Add-Package /PackagePath:"D:\TEMP\Updatesx64\Updates\Windows7-x64\General\Windows6.1-KB2820331-x64.msu" /ScratchDir:"C:\Windows\Temp\WinToolkit\ScratchDir" /EnglishDeployment Image Servicing and Management toolVersion: 6.1.7600.16385Image Version: 6.1.7600.16385Processing 1 of 1 - D:\TEMP\Updatesx64\Updates\Windows7-x64\General\Windows6.1-KB2820331-x64.msu: An error occurred applying the Unattend.xml file from the .msu package.For more information, review the log file. Error: 0x800f0830Error: 0x800f0830DISM failed. No operation was performed.For more information, review the log file.The DISM log file can be found at C:\Windows\Logs\DISM\dism.logD:\SOFTWARE\WINTOOLKIT>exit---------------------------------- Quote Link to comment Share on other sites More sharing options...
Etz Posted June 3, 2014 Share Posted June 3, 2014 Post Dism.log aswell... (C:\Windows\Logs\DISM\dism.log) Quote Link to comment Share on other sites More sharing options...
© KEiGHT Posted June 3, 2014 Author Share Posted June 3, 2014 (edited) Dism.log Edited June 3, 2014 by © KEiGHT Quote Link to comment Share on other sites More sharing options...
Legolash2o Posted June 3, 2014 Share Posted June 3, 2014 Only thing I can recommend is do it without those updates. If i remember correctly, it's usually the update which integrated before them which causes the problem (last successful). Quote Link to comment Share on other sites More sharing options...
© KEiGHT Posted June 3, 2014 Author Share Posted June 3, 2014 (edited) With earlier versions, nothing has happened with these updates, why now ? All of them till now, with issues ! Windows6.1-KB2820331-x64Windows6.1-KB2823655-v2-x64Windows6.1-KB2823655-v2-x64Windows6.1-KB2819485-x64 Edited June 3, 2014 by © KEiGHT Quote Link to comment Share on other sites More sharing options...
© KEiGHT Posted June 3, 2014 Author Share Posted June 3, 2014 (edited) the updates issues still growing at numbers ! Edited June 3, 2014 by © KEiGHT Quote Link to comment Share on other sites More sharing options...
© KEiGHT Posted June 4, 2014 Author Share Posted June 4, 2014 Finally, the last version is FINE ! good work Liam ! Thanks :lock: Legolash2o 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.