RicaNeaga Posted February 20, 2015 Share Posted February 20, 2015 Hello! Sorry I was out for such a long period, I was busy with a new job. Also, until now, WinToolkit worked perfectly, so I hadn't any reason to complain See below the error - when trying to integrate 3025980 in an untouched Windows 7 HP x86 image, that error appeared. Can you please solve it soon? Thanks Title: 1 error(s) have occurredErrType: ErrorDescription: Win Toolkit has recorded errors which occurred during integration and have been stored via '>> Details'.Exception: An error occurred whilst integrating an update!Exception:Microsoft Windows [Version 6.1.7601]Copyright (c) 2009 Microsoft Corporation. All rights reserved.C:\Users\Administrator\Desktop\WinToolkit_1.5.3.12_Portable>chcp 65001C:\Users\Administrator\Desktop\WinToolkit_1.5.3.12_Portable>Set SEE_MASK_NOZONECHECKS=1C:\Users\Administrator\Desktop\WinToolkit_1.5.3.12_Portable>"C:\Windows\System32\Dism.exe" /Image:"C:\WinToolkit_Mount_150E41B91B105582D50C56EFD312D6B5" /Add-Package /PackagePath:"C:\7lite\Updates\McRip Windows 7 x86\Windows6.1-KB3025980-x86.msu" /ScratchDir:"C:\Windows\WinToolkit_Temp\ScratchDir_542C68CAB34E6A9D59337580544FA734" /EnglishDeployment Image Servicing and Management toolVersion: 6.1.7600.16385Image Version: 6.1.7601.18489Processing 1 of 1 - C:\7lite\Updates\McRip Windows 7 x86\Windows6.1-KB3025980-x86.msu: An error occurred while expanding the .msu package into the temporary folder, C:\Windows\WinToolkit_Temp\ScratchDir_542C68CAB34E6A9D59337580544FA734\126885E7-309C-4385-BBBA-E523FEF4F541. Error: 0x8007065eError: 1630Data of this type is not supported.The DISM log file can be found at C:\Windows\Logs\DISM\dism.logC:\Users\Administrator\Desktop\WinToolkit_1.5.3.12_Portable>exit---------------------------------- Quote Link to comment Share on other sites More sharing options...
ianymaty Posted February 21, 2015 Share Posted February 21, 2015 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. RicaNeaga 1 Quote Link to comment Share on other sites More sharing options...
abbodi1406 Posted February 21, 2015 Share Posted February 21, 2015 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 RicaNeaga 1 Quote Link to comment Share on other sites More sharing options...
RicaNeaga Posted February 21, 2015 Author Share Posted February 21, 2015 No problem, going to extract and retry the integration process. Thanks to both Quote Link to comment Share on other sites More sharing options...
RicaNeaga Posted February 28, 2015 Author Share Posted February 28, 2015 Sorry for the late reply. Everything was great after unarchiving. Thanks alot! Ticket closed. 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.