none
Unable to locate package source. When downloading Visual Studio 2012 Update 2

    Question

  • Hello,

    I tried to get the downloaded Visual Studio 2012 Update 2; via the /layout option.  But the downloading comes to halt when it trying to get the package source for "Windows App Certification Kit Native Components-x64_en-us.msp".  Any idea how to proceed the downloads?  Thanks in advance.

    

    Friday, April 05, 2013 5:45 PM

Answers

  • This is a similar problem that occurred with Update 1.  (I.e., its occurring with the same Windows App Cert Kit files.)

    On my XP system that I'm using to download (and build an ISO), the bootstrapper created a temp folder named:

         C:\Documents and Settings\Steve\Local Settings\Temp\{2fba7dd0-b8eb-4185-aea3-e6910d3f8102}

    (The GUID seems to be the same during repeated runs.)

    Within the {guid} folder there are .ba1 and .be subfolders.  The .be folder contains the patch installer, while the .ba folder contains all the bootstrapper (downloader) executables and metadata.  In particular, the file named BootstrapperApplicationData.xml identifies all the files that will be downloaded.

    The way this bootstrapper works is by using BITS to download each file (into the {guid} folder) as a hidden file named BIT###.tmp (where ### is a 3 digit hex. ascending counter).  After download of a file completes, it gets renamed to the appropiate filename and then its moved to the target layout folder.

    What's happening here is that the four files fail Authenticode verification and the files don't get renamed or moved.  This was seen within the log file named dd_vsupdate_KB2707250_xxx.log.  For instance, my log file contained:

    Error 0x8009200d: Failed authenticode verification of payload:
                      C:\DOCUME~1\Steve\LOCALS~1\Temp\{2fba7dd0-b8eb-4185-aea3-e6910d3f8102}\WinACK_x64_x86_en
    Error 0x8009200d: Failed to verify payload signature:
                      J:\Steve\Microsoft\Visual Studio\2012\U2 (2012.2)\Ultimate\Layout\packages\WinACK\Windows App Certification Kit x64-x86_en-us.msp
    Error 0x8009200d: Failed to layout payload from cached payload:
                      J:\Steve\Microsoft\Visual Studio\2012\U2 (2012.2)\Ultimate\Layout\packages\WinACK\Windows App Certification Kit x64-x86_en-us.msp

    Thus, when the errors occured, I navigated to the user\Local\Temp\{guid} directory, renamed the file, and copied it to the target Layout\packages\WinACK folder (which I had to create), then clicked Retry in the dialog.  I needed to do this for each of the four files affected.

    The four files that needed renaming and copying on-the-fly were:

    WinACK_native_x64_en  -->  Windows App Certification Kit Native Components-x64_en-us.msp
    WinACK_native_x86_en  -->  Windows App Certification Kit Native Components-x86_en-us.msp
    WinACK_x64_x86_en     -->  Windows App Certification Kit x64-x86_en-us.msp
    WinACK_x86_x86_en     -->  Windows App Certification Kit x86-x86_en-us.msp

    (The four errors encountered were in the above order...)

    In case you've already got everything in your Layout folder except for these four files, the source files can be downloaded from:

         http://go.microsoft.com/fwlink/?LinkId=283370&clcid=0x409
         http://go.microsoft.com/fwlink/?LinkId=283371&clcid=0x409
         http://go.microsoft.com/fwlink/?LinkId=283372&clcid=0x409
         http://go.microsoft.com/fwlink/?LinkId=283373&clcid=0x409

    as indicated within the log file.  (Just make sure they get placed into a packages\WinACK subfolder...)

    Since the SAME EXACT FILES had a similar issue in the bootstrapper for Update 1, I thought it would have been fixed for this update.  After I complained the last time, it's apparent no one took the time to properly diagnose and fix it.  (Maybe this only occurs when using an XP system for download?  Or maybe this has something to do with the way the metadata is built?  Or how the deployment server's asset tree is populated?  Its awfully suspicious that it's been the same four files each time that have this "can't be located" 'cause of screwed-up Authenticode verification problem.)

    Of course, this nonsense (i.e., reverse engineering the downloader)...and the ill will it generates...could all be avoided by distributing these updates as ISO images!  (Reliance on deployment servers or CDNs to deliver the files has proven to be ROUTINELY PROBLEMATIC.)


    Saturday, April 06, 2013 12:37 AM
  • I cancelled the update, installed these two, then started the update again.  Worked fine.  Thanks for the links.

    http://go.microsoft.com/fwlink/?LinkId=283370&clcid=0x409

    http://go.microsoft.com/fwlink/?LinkId=283372&clcid=0x409

    Tuesday, April 16, 2013 1:43 PM
  • You should look into the C:\Users\[Username]\AppData\Local\Temp folder, and find the last changed file, it must be dd_vsupdate_KB2707250_.....log

    On the last lines of this log you will find link to needed file. Download it manually, and then press "..." button in Update dialog, and select it.

    Then installation process proceeds to next file (check it's name in log, download, an select, just as previous one).

    For me (Windows 7 Prof.), theese files was:

    http://go.microsoft.com/fwlink/?LinkId=283367

    http://go.microsoft.com/fwlink/?LinkId=283366

    http://go.microsoft.com/fwlink/?LinkId=283365

    http://go.microsoft.com/fwlink/?LinkId=283039


    Tuesday, April 09, 2013 4:31 PM

All replies

  • Ditto.  This is really aggravating.
    Friday, April 05, 2013 7:09 PM
  • I have the same issue.  Here is the relevant portion of the log file:

    <code>
    
    [1548:0C38][2013-04-05T11:24:11]: MUX:  Package:WinACK_native_x64_en, PayloadId:WinACK_native_x64_en Url: http://go.microsoft.com/fwlink/?LinkId=283370&clcid=0x409, Attempting count: 1
    [1548:0C38][2013-04-05T11:24:11]: MUX:  Existing last unconfirmed source: Web
    [1548:0C38][2013-04-05T11:24:11]: Acquiring package: WinACK_native_x64_en, payload: WinACK_native_x64_en, download from: http://go.microsoft.com/fwlink/?LinkId=283370&clcid=0x409
    [1548:0C38][2013-04-05T11:24:15]: Error 0xc000000d: Failed authenticode verification of payload: C:\Users\Me\AppData\Local\Temp\{2fba7dd0-b8eb-4185-aea3-e6910d3f8102}\WinACK_native_x64_en
    [1548:0C38][2013-04-05T11:24:15]: Error 0xc000000d: Failed to verify payload signature: C:\MSDN\VS2012\Update2\packages\WinACK\Windows App Certification Kit Native Components-x64_en-us.msp
    [1548:0C38][2013-04-05T11:24:15]: Error 0xc000000d: Failed to layout payload from cached payload: C:\MSDN\VS2012\Update2\packages\WinACK\Windows App Certification Kit Native Components-x64_en-us.msp
    [1548:0C38][2013-04-05T11:24:15]: MUX:  Set Result: Return Code=-1073741811 (0xC000000D), Error Message=, Result Detail=, Vital=False, Package Action=Verify, Package Id=WinACK_native_x64_en
    [1548:0C38][2013-04-05T11:24:15]: Failed to layout payload: WinACK_native_x64_en to layout directory: C:\MSDN\VS2012\Update2\, error: 0xc000000d.
    [1548:0C38][2013-04-05T11:24:15]: Application requested retry of payload: WinACK_native_x64_en, encountered error: 0xc000000d. Retrying...
    [1548:0C38][2013-04-05T11:24:15]: Prompt for source of package: WinACK_native_x64_en, payload: WinACK_native_x64_en, path: C:\MSDN\VS2012\Update2\packages\WinACK\Windows App Certification Kit Native Components-x64_en-us.msp
    [1548:0C38][2013-04-05T11:24:15]: MUX:  Next Source: Web, Attempted: 2, Limit:3
    [1548:0C38][2013-04-05T11:24:15]: MUX:  Source retrieved: Web
    [1548:0C38][2013-04-05T11:24:15]: MUX:  Sleep for 3 seconds before retrying
    
    
    </code>

    Friday, April 05, 2013 7:32 PM
  • While the install error is still visible (ie do not cancel installation) - ty opening a command window, navigating to the root dir and searching for the file in question. For example:

    C:\>dir /s "Windows App Certification Kit Native Components-x64_en-us.msp"

    If found, browse to the file using that option on the installer page and press 'retry'.

    I had the same issue - but for a different file - and managed to complete the installation by manually locating the package in question (for me it was 'webtoolsextensionsvs.msi')

    Good luck!

    • Proposed as answer by a.m.jlive Friday, December 06, 2013 4:01 PM
    Friday, April 05, 2013 9:07 PM
  • This is a similar problem that occurred with Update 1.  (I.e., its occurring with the same Windows App Cert Kit files.)

    On my XP system that I'm using to download (and build an ISO), the bootstrapper created a temp folder named:

         C:\Documents and Settings\Steve\Local Settings\Temp\{2fba7dd0-b8eb-4185-aea3-e6910d3f8102}

    (The GUID seems to be the same during repeated runs.)

    Within the {guid} folder there are .ba1 and .be subfolders.  The .be folder contains the patch installer, while the .ba folder contains all the bootstrapper (downloader) executables and metadata.  In particular, the file named BootstrapperApplicationData.xml identifies all the files that will be downloaded.

    The way this bootstrapper works is by using BITS to download each file (into the {guid} folder) as a hidden file named BIT###.tmp (where ### is a 3 digit hex. ascending counter).  After download of a file completes, it gets renamed to the appropiate filename and then its moved to the target layout folder.

    What's happening here is that the four files fail Authenticode verification and the files don't get renamed or moved.  This was seen within the log file named dd_vsupdate_KB2707250_xxx.log.  For instance, my log file contained:

    Error 0x8009200d: Failed authenticode verification of payload:
                      C:\DOCUME~1\Steve\LOCALS~1\Temp\{2fba7dd0-b8eb-4185-aea3-e6910d3f8102}\WinACK_x64_x86_en
    Error 0x8009200d: Failed to verify payload signature:
                      J:\Steve\Microsoft\Visual Studio\2012\U2 (2012.2)\Ultimate\Layout\packages\WinACK\Windows App Certification Kit x64-x86_en-us.msp
    Error 0x8009200d: Failed to layout payload from cached payload:
                      J:\Steve\Microsoft\Visual Studio\2012\U2 (2012.2)\Ultimate\Layout\packages\WinACK\Windows App Certification Kit x64-x86_en-us.msp

    Thus, when the errors occured, I navigated to the user\Local\Temp\{guid} directory, renamed the file, and copied it to the target Layout\packages\WinACK folder (which I had to create), then clicked Retry in the dialog.  I needed to do this for each of the four files affected.

    The four files that needed renaming and copying on-the-fly were:

    WinACK_native_x64_en  -->  Windows App Certification Kit Native Components-x64_en-us.msp
    WinACK_native_x86_en  -->  Windows App Certification Kit Native Components-x86_en-us.msp
    WinACK_x64_x86_en     -->  Windows App Certification Kit x64-x86_en-us.msp
    WinACK_x86_x86_en     -->  Windows App Certification Kit x86-x86_en-us.msp

    (The four errors encountered were in the above order...)

    In case you've already got everything in your Layout folder except for these four files, the source files can be downloaded from:

         http://go.microsoft.com/fwlink/?LinkId=283370&clcid=0x409
         http://go.microsoft.com/fwlink/?LinkId=283371&clcid=0x409
         http://go.microsoft.com/fwlink/?LinkId=283372&clcid=0x409
         http://go.microsoft.com/fwlink/?LinkId=283373&clcid=0x409

    as indicated within the log file.  (Just make sure they get placed into a packages\WinACK subfolder...)

    Since the SAME EXACT FILES had a similar issue in the bootstrapper for Update 1, I thought it would have been fixed for this update.  After I complained the last time, it's apparent no one took the time to properly diagnose and fix it.  (Maybe this only occurs when using an XP system for download?  Or maybe this has something to do with the way the metadata is built?  Or how the deployment server's asset tree is populated?  Its awfully suspicious that it's been the same four files each time that have this "can't be located" 'cause of screwed-up Authenticode verification problem.)

    Of course, this nonsense (i.e., reverse engineering the downloader)...and the ill will it generates...could all be avoided by distributing these updates as ISO images!  (Reliance on deployment servers or CDNs to deliver the files has proven to be ROUTINELY PROBLEMATIC.)


    Saturday, April 06, 2013 12:37 AM
  • Thanks!!!!!!! 
    Sunday, April 07, 2013 9:55 AM
  • For 64-bit Windows 7 Enterprise Edition, using the download links:

    http://go.microsoft.com/fwlink/?LinkId=283370&clcid=0x409

    http://go.microsoft.com/fwlink/?LinkId=283372&clcid=0x409

    and saving to:

    C:\Users\[your username here]\AppData\Local\Microsoft\Windows\Temporary Internet Files\Content.IE5\5MJI8EYP\packages\WinACK

    prior to hitting retry on the VS2012.2.exe installer, did the trick.  Had to create the two subfolders "\packages\WinACK" in the "5MJI8EYP" folder during the file download and save operation.

    Prior to that I wasted time looking around in

    C:\Users\[your username here]\AppData\Local\Temp\1\{2fba7dd0-b8eb-4185-aea3-e6910d3f8102}\.ba1\

    but didn't find any .tmp files to rename and relocate.  (Perhaps a difference between Win7 and XP?)  Hopefully this saves others a bit of frustration. 

    Monday, April 08, 2013 6:55 PM
  • After getting past the retry error, the installer finished, but displayed:

    

    What does this mean?  Success or failure?

    If the installer took the two .msp files and continued, why an error message?

    Apparently one or both are "non-vital" so if they don't get installed the installer will continue?

    [3354:2648][2013-04-08T11:43:47]: Applied non-vital package: WinACK_x64_x86_en, encountered error: 0xc000000d. Continuing...
    [3354:3D2C][2013-04-08T11:43:47]: Skipping apply of package: WinACK_x64_x86_en due to cache error: 0xc000000d. Continuing...

    But the installer never asked me if I wanted to give up and skip the packages.  I guess it made the decision for me?

    Monday, April 08, 2013 7:16 PM
  • Same issue. No solution so far.

    MS created a problem instead of putting ISO or direct link at least ot MSDN. Why it is not available through WSUS updates?

    Microsoft's excuses don't interest me.

    Monday, April 08, 2013 9:14 PM
  • Same here.
    Tuesday, April 09, 2013 11:27 AM
  • You should look into the C:\Users\[Username]\AppData\Local\Temp folder, and find the last changed file, it must be dd_vsupdate_KB2707250_.....log

    On the last lines of this log you will find link to needed file. Download it manually, and then press "..." button in Update dialog, and select it.

    Then installation process proceeds to next file (check it's name in log, download, an select, just as previous one).

    For me (Windows 7 Prof.), theese files was:

    http://go.microsoft.com/fwlink/?LinkId=283367

    http://go.microsoft.com/fwlink/?LinkId=283366

    http://go.microsoft.com/fwlink/?LinkId=283365

    http://go.microsoft.com/fwlink/?LinkId=283039


    Tuesday, April 09, 2013 4:31 PM
  • On my system, the error was specifically that the downloaded MSPs' PKI signatures terminated in a root certificate that was not trusted on my system.  It was a certificate trust issue.  In theory if you have the same problem, you could add the root certificate that was used to sign these packages to your Trusted Root certificates store, and that would allow the installation to work.  However, I don't particularly care about these exact packages so I have not bothered trying to reapply them.

    R/Don//

    Thursday, April 11, 2013 2:30 PM
  • I am getting the same warning as Saravannah Phillips mentioned previously.

    Prior to this, I located the Windows Certification Kit on my computer (I noticed that there was a Windows Kits folder on my start menu) and pasted the following path into the VS2012 Update 2 installation window when prompted. I had to do this several times for different components and the installation eventually completes, at which point the warning is displayed.

    C:\Program Files (x86)\Windows Kits\8.0\App Certification Kit\appcert.exe

    I'm not clear whether this is a critcal problem, just a warning or how to resolve it?

    Note: I installed on a machine running Windows 7 Professional 64bit.

    Friday, April 12, 2013 12:53 PM
  • I cancelled the update, installed these two, then started the update again.  Worked fine.  Thanks for the links.

    http://go.microsoft.com/fwlink/?LinkId=283370&clcid=0x409

    http://go.microsoft.com/fwlink/?LinkId=283372&clcid=0x409

    Tuesday, April 16, 2013 1:43 PM
  • Hi All,

    Thank you for participate in this thread and share your solution here. If you still have the same problem, please reopen a new case and remember to desribe your OS info on the new thread. I will close this case according to our policy because op's not back. I will also mark those worked solutions for you.

    Regards,


    Barry Wang
    MSDN Community Support | Feedback to us
    Develop and promote your apps in Windows Store
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.

    Thursday, April 25, 2013 8:11 AM
  • I downloaded the windows 8 SDK (Windows SDK for Windows 8) @ http://msdn.microsoft.com/en-us/windows/desktop/hh852363.aspx (download time: 3 hrs +-)

    I had chosen the standalone version for the SDK download, so the C:\Users\[username]\Downloads\Windows Kits\8.0\StandaloneSDK\ folder was created.


    The needed installers were @ C:\Users\[username]\Downloads\Windows Kits\8.0\StandaloneSDK\Patches\8.59.29750 folder.

    Hope this helps.

    Windows 2008 R2 server x64 with Visual studio 2012 Ultimate, trying install update 2
    Wednesday, May 08, 2013 6:57 PM
  • I cancelled the update, installed these two, then started the update again.  Worked fine.  Thanks for the links.

    http://go.microsoft.com/fwlink/?LinkId=283370&clcid=0x409

    http://go.microsoft.com/fwlink/?LinkId=283372&clcid=0x409

    It has not worked for me. But it doesn't matter, SteveHall's post helped. SteveHall, thank you! :)

    So... I got this error with VS11 Update 2, with Update 3 RC and with Update 2 RC 2... Is anyone going to fix it? :D


    • Edited by Brigadir Saturday, June 01, 2013 12:16 PM
    Saturday, June 01, 2013 12:14 PM
  • worked great!  Thanks!
    Friday, June 21, 2013 7:23 PM
  • This worked great for me - except this was the path I needed to use:

    C:\Program Files\Windows Kits\8.0\App Certification Kit\appcert.exe

    Thursday, June 27, 2013 6:27 PM
  • Its happening for me with VS2012 Update 3 as well.

    Monday, July 08, 2013 1:19 PM
  • And Update 4 has the same issue. I cannot belive why the installer is not able to download stuff from the internet and we have to do it manually.

    The installer should first check the forum and then error out ;-).

    Monday, December 30, 2013 10:23 AM
  • Is there a solution for VS 2012 Update 4?
    Tuesday, February 18, 2014 9:58 PM