I have observed the following behaviour with Visual Studio 2012 on Windows 7 and Windows 8, and Visual Studio 2013 on Windows 7.
The issue I'm describing does not occur with Visual Studio 2010 on either of Windows XP nor Windows 7. The problem looks to be associated with Visual Studio 2012 and Visual Studio 2013 only.
There seems to be a problem with the .zip file created by the "Export Template..." wizard. The wizard itself runs without any errors and creates the .zip file in the "Exported Templates" folder, but when I try to extract the files (in order to modify the template as instructed here: http://msdn.microsoft.com/en-us/library/ms185319(v=vs.110).aspx) I get the following error message:
Extracting file: C:\Users\me\Documents\Visual Studio 2012\My Exported Templates\Sample.Web.zip
Extracting to "C:\Users\me\Documents\Visual Studio 2012\My Exported Templates\Sample.Web\"
Use Path: yes Overlay Files: no
Central and local directory mismatch for file "App_GlobalResources/" (crc-32 - local: CA1525D6 hex central: 0 hex).
Local and central CRC values don't match
When I look into the folder where I was attempting to extract the template, I see that it contains the project file 'Sample.Web.csproj' but nothing else.
The above output was produced by Winzip v15.5, using a web project. I get a slightly different error with a class library project (directory mismatch for the 'Properties' folder instead of the 'App_GlobalResources' folder).
Several other people in the office where I am working have the same problem, but different compression utilities produce similar errors with a slightly different level of detail. They all report a crc error, however.
Using WinZip (and 7Zip) the archive can be opened and viewed, and individual files can be extracted, but it seems to have a problem with folders.
I have a different machine, also running Windows 7, with Visual Studio 2010 installed. On that machine, I do not receive this error. I have been customising and using multi-project templates With Visual Studio 2010 and Visual Studio 2008 for a couple of years using the exact same procedure and have never encountered this problem before.