Develop Reference

Clickonce WPF Windows 7 - The application is improperly formatted.

I have a machine with a clean install of Windows 7 where I want to install my app.
I've built a WPF App on Windows 10 with prerequisites of .NET 4.5 and Visual C++ Redistributable Packages for Visual Studio 2013
I've included them in my Clickonce installer as Prerequisites:
If I attempt to run the .application file that is generated from Clickonce on the Windows 7 machine, I get the following error:
Cannot Continue. The application is improperly formatted. Contact the
application vendor for assistance.
However, I run the setup.exe on my Windows 7 machine it correctly prompts that it needs to install .NET 4.5 and Visual C++ Redistributable Packages for Visual Studio 2013. It then successfully goes through the install process for each Prerequisite.
Except, after the Prerequisites are installed, I receive the same The application is improperly formatted. error from above.
If I then re-run the .application file it will finally install.
Either way, this is definitely not a good user experience. Is this something to do with building the App on Windows 10 and attempting to install on Windows 7?
I've seen this question which seems similar, however I am installing .NET 4.5 as a prerequisite:
Manifest may not be valid or the file could not be opened.
Below are the error details:
PLATFORM VERSION INFO
Windows : 6.1.7601.65536 (Win32NT)
Common Language Runtime : 2.0.50727.5420
System.Deployment.dll : 2.0.50727.5420 (Win7SP1.050727-5400)
mscorwks.dll : 2.0.50727.5420 (Win7SP1.050727-5400)
dfdll.dll : 2.0.50727.4927 (NetFXspW7.050727-4900)
dfshim.dll : 4.0.40305.0 (Main.040305-0000)
SOURCES
Deployment url : file:///C:/Users/BHS/Desktop/New%20folder/BHSScaleOps.application
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of C:\Users\BHS\Desktop\New folder\BHSScaleOps.application resulted in exception. Following failure messages were detected:
+ Exception reading manifest from file:///C:/Users/BHS/Desktop/New%20folder/BHSScaleOps.application: the manifest may not be valid or the file could not be opened.
+ Manifest XML signature is not valid.
+ SignatureDescription could not be created for the signature algorithm supplied.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [3/21/2017 4:20:01 PM] : Activation of C:\Users\BHS\Desktop\New folder\BHSScaleOps.application has started.
ERROR DETAILS
Following errors were detected during this operation.
* [3/21/2017 4:20:01 PM] System.Deployment.Application.InvalidDeploymentException (ManifestParse)
- Exception reading manifest from file:///C:/Users/BHS/Desktop/New%20folder/BHSScaleOps.application: the manifest may not be valid or the file could not be opened.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
--- Inner Exception ---
System.Deployment.Application.InvalidDeploymentException (SignatureValidation)
- Manifest XML signature is not valid.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
at System.Deployment.Application.ManifestReader.FromDocument(String localPath, ManifestType manifestType, Uri sourceUri)
--- Inner Exception ---
System.Security.Cryptography.CryptographicException
- SignatureDescription could not be created for the signature algorithm supplied.
- Source: System.Security
- Stack trace:
at System.Security.Cryptography.Xml.SignedXml.CheckSignedInfo(AsymmetricAlgorithm key)
at System.Security.Cryptography.Xml.SignedXml.CheckSignatureReturningKey(AsymmetricAlgorithm& signingKey)
at System.Deployment.Internal.CodeSigning.SignedCmiManifest.Verify(CmiManifestVerifyFlags verifyFlags)
at System.Deployment.Application.Manifest.AssemblyManifest.ValidateSignature(Stream s)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Your manifest is signed using SHA-256. When you try to install the ClickOnce application on a machine which has only .NET 4.0 installed you receive the Manifest XML signature is not valid error you mentioned because up to .NET 4.0 SHA-1 is expected.
This is why after you successfully installed .NET 4.5 as prerequisite everything works fine. I have no idea why this isn't working in a single step but requires two steps instead. Perhaps this relates to a restart required after installing the new framework version?
The solution is to use SHA-1 when signing your manifest. You can find information on how to achieve this in this answer from Miroslav Nedyalkov.

Strong name signature not valid for this assembly stdole.dll

I've just started to get the following error in my ClickOnce application. When installing and running the same application, after seemingly successful installation I get an error message:
Application Validation did not succeed
The error details I can see the problem to be:
Strong name signature not valid for this assembly stdole.dll.
When i click into details I get
ERROR DETAILS Following errors were detected during this operation.
* [04/13/2016 11:33:22 AM] System.Deployment.Application.InvalidDeploymentException
(SignatureValidation)
- Strong name signature not valid for this assembly stdole.dll.
- Source: System.Deployment
- Stack trace: at System.Deployment.Application.ComponentVerifier.VerifyStrongNameAssembly(String
filePath, AssemblyManifest assemblyManifest) at
System.Deployment.Application.ComponentVerifier.VerifyComponents()
at
System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState
subState, AssemblyManifest deployManifest, AssemblyManifest
appManifest, Uri sourceUriBase, String targetDirectory, String group,
IDownloadNotification notification, DownloadOptions options) at
System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState
subState, ActivationDescription actDesc, Int64 transactionId,
TempDirectory& downloadTemp) at
System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState&
subState, ActivationDescription actDesc) at
System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri
activationUri, Boolean isShortcut, String textualSubId, String
deploymentProviderUrlFromExtension, BrowserSettings browserSettings,
String& errorPageUrl) at
System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object
state)

Hey Not sure if you still haven't figured out the problem but please refer to this article: strong-name-signature-not-valid-for-this-assembly-stdole-dll and apply it depending on the version of Visual Studio you are using.
The Problem is that the ClickOnce application is trying to use an unsigned version of the stdole dll but you need to have that signed.
Details from the webpage:
Open path “C:\Program Files (x86)\Microsoft Visual Studio 9.0\Visual Studio Tools for Office\PIA\Office11” and “C:\Program Files (x86)\Microsoft Visual Studio 9.0\Visual Studio Tools for Office\PIA\Office12”, there is file stdole.dll wich was 16kb large and not signed
Open the path “C:\Program Files (x86)\Microsoft.NET\Primary Interop Assemblies”, there is file stdole.dll wich was 25kb large and signed
Replaced the unsigned dlls with the signed ones and did another publish

This is a remarkably insidious problem that will sneak up on you again and again (dev boxes, build machines, etc). For whatever reason Microsoft keeps an old unsigned version of the assembly in the Visual Studio assembly search path.
Check out Why is Visual Studio 2015 adding stdole.dll and Microsoft.AnalysisServices.AdomdClient.dll to my project? for some more details and some answers which may help avoid this in the future.

error with application manifest created by MageUI

i have made a project in Net 4.0,c# win application; using MageUI.exe i have created and application and deployment manifest in this way:
i have saved my output release project in a local dir (C:\Users\Gio\Desktop\ClickOnceDeploy\Application Files\Evolution_1_0_0_0), then with MageUI.exe i have created new application manifest ,setting Name and description value, x86 processor; in tab files i have set my local dir path, then i have populated grid Application(through button populate) and i have saved application manifest(Evolution.exe.manifest) in my local dir with my output release files.
after i have created new deployment manifest setting the same application manifest Name and description,x86 processor and in tab deployment options in start location i have set my share dir :
"\srvnas2\gio\testDeploy\Application Files\Evolution.application".
Then in Apllication reference tab, i have selected application manifest in my local dir.
I have saved my deployment manifest, moving up one directory to the root of my local dir (in C:\Users\Gio\Desktop\ClickOnceDeploy\Application Files).
after this, i have copied all my local dir contents in share dir
(\srvnas2\gio\testDeploy\Application Files) and then i have clicked Evolution.application as setup.
a popup told me to install my application and after clicking install button, i have got InvalidDeploymentException error:
Errors detail:
PLATFORM VERSION INFO
Windows : 6.1.7601.65536 (Win32NT)
Common Language Runtime : 4.0.30319.18444
System.Deployment.dll : 4.0.30319.34244 built by: FX452RTMGDR
clr.dll : 4.0.30319.18444 built by: FX451RTMGDR
dfdll.dll : 4.0.30319.34244 built by: FX452RTMGDR
dfshim.dll : 4.0.31106.0 (Main.031106-0000)
SOURCES
Deployment url : file://srvnas2/gio/testDeploy/Application%20Files/Evolution.application
Deployment Provider url : file://srvnas2/gio/testDeploy/Application%20Files/Evolution.application
Application url : file://srvnas2/gio/testDeploy/Application%20Files/Evolution_1_0_0_0/Evolution.exe.manifest
IDENTITIES
Deployment Identity : Evolution.app, Version=1.0.0.0, Culture=neutral, PublicKeyToken=fe14ca94139b6fbf, processorArchitecture=x86
Application Identity : Evolution.exe, Version=1.0.0.0, Culture=neutral, PublicKeyToken=fe14ca94139b6fbf, processorArchitecture=x86, type=win32
APPLICATION SUMMARY
* Installable application.
RIEPILOGO ERRORI
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of \\srvnas2\gio\testDeploy\Application Files\Evolution.application resulted in exception. Following failure messages were detected:
+ Reference in the manifest does not match the identity of the downloaded assembly Evolution.exe.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
STATO OPERAZIONE
* [03/02/2015 14:49:59] : Activation of \\srvnas2\gio\testDeploy\Application Files\Evolution.application avviata.
* [03/02/2015 14:49:59] : Processing of deployment manifest has successfully completed
* [03/02/2015 14:49:59] : Installation of the application has started.
* [03/02/2015 14:49:59] : Processing of application manifest has successfully completed.
* [03/02/2015 14:50:02] : Found compatible runtime version 4.0.30319.
* [03/02/2015 14:50:02] : Request of trust and detection of platform is complete.
ERROR DETAILS
Following errors were detected during this operation.
* [03/02/2015 14:50:05] System.Deployment.Application.InvalidDeploymentException (RefDefValidation)
- Reference in the manifest does not match the identity of the downloaded assembly Evolution.exe.
- Source: System.Deployment
- stack:
in System.Deployment.Application.DownloadManager.ProcessDownloadedFile(Object sender, DownloadEventArgs e)
in System.Deployment.Application.FileDownloader.DownloadModifiedEventHandler.Invoke(Object sender, DownloadEventArgs e)
in System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
in System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
in System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
in System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
in System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
in System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
in System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
in System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.
i have seen in web to found a solution but i haven't found it, have you any suggest?

After investigating this issue, I found that this issue occurs due to a manifest being embedded into the executable while building the application.
So i created an application without manifest and worked perfectly.

Strong name signature not valid for this assembly Microsoft.Practices.EnterpriseLibrary.Data.dll

I am running windows form application as ClickOnce Deployment. When i debugg the solution
i am not getting any error. it's working fine.
But, when i publish the application using click once deployment and run the application from
folder, i am getting the following error log.
Can anyone help me out what exactly the problem is?
The Dll's are in assemblies folder in one of the project.And they are used in other project as reference.
PLATFORM VERSION INFO
Windows : 6.1.7601.65536 (Win32NT)
Common Language Runtime : 4.0.30319.18063
System.Deployment.dll : 4.0.30319.17929 built by: FX45RTMREL
clr.dll : 4.0.30319.18063 built by: FX45RTMGDR
dfdll.dll : 4.0.30319.17929 built by: FX45RTMREL
dfshim.dll : 4.0.41209.0 (Main.041209-0000)
SOURCES
Deployment url : WorkPC/FaxPromptTool/xrm.OutboundFax.application
Server : Microsoft-IIS/7.5
X-Powered-By : ASP.NET
Application url : WorkPC/FaxPromptTool/Application%20Files/xrm.OutboundFax_1_0_0_5/xrm.OutboundFax.exe.manifest
Server : Microsoft-IIS/7.5
X-Powered-By : ASP.NET
IDENTITIES
Deployment Identity : xrm.OutboundFax.application, Version=1.0.0.5, Culture=neutral, PublicKeyToken=f841479c30c8d3cb, processorArchitecture=x86
Application Identity : xrm.OutboundFax.exe, Version=1.0.0.5, Culture=neutral, PublicKeyToken=f841479c30c8d3cb, processorArchitecture=x86, type=win32
APPLICATION SUMMARY
* Online only application.
* Trust url parameter is set.
ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://pc265075/FaxPromptTool/xrm.OutboundFax.application resulted in exception. Following failure messages were detected:
+ Strong name signature not valid for this assembly Microsoft.Practices.EnterpriseLibrary.Data.dll.
COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.
WARNINGS
There were no warnings during this operation.
OPERATION PROGRESS STATUS
* [09/23/14 8:53:12 PM] : Activation of http://pc265075/FaxPromptTool/xrm.OutboundFax.application has started.
* [09/23/14 8:53:12 PM] : Processing of deployment manifest has successfully completed.
* [09/23/14 8:53:12 PM] : Installation of the application has started.
* [09/23/14 8:53:12 PM] : Processing of application manifest has successfully completed.
* [09/23/14 8:53:16 PM] : Found compatible runtime version 4.0.30319.
* [09/23/14 8:53:16 PM] : Request of trust and detection of platform is complete.
ERROR DETAILS
Following errors were detected during this operation.
* [09/23/14 8:53:17 PM] System.Deployment.Application.InvalidDeploymentException (SignatureValidation)
- Strong name signature not valid for this assembly Microsoft.Practices.EnterpriseLibrary.Data.dll.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.ComponentVerifier.VerifyStrongNameAssembly(String filePath, AssemblyManifest assemblyManifest)
at System.Deployment.Application.ComponentVerifier.StrongNameAssemblyComponent.Verify()
at System.Deployment.Application.ComponentVerifier.VerifyComponents()
at System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState subState, AssemblyManifest deployManifest, AssemblyManifest appManifest, Uri sourceUriBase, String targetDirectory, String group, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState subState, ActivationDescription actDesc, Int64 transactionId, TempDirectory& downloadTemp)
at System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState& subState, ActivationDescription actDesc)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut, String textualSubId, String deploymentProviderUrlFromExtension, BrowserSettings browserSettings, String& errorPageUrl)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

I faced the same issue when I did click once deployment. The possible errors are the property settings are wrong.
1.Did u strong name this assembly?.
After strong naming did you delete the old reference and add a new one ? If so that's wrong. We need not explicitly add the dll again. Once we build it ll get referred automatically.
If you have removed the reference added explicitly then check the below condition,
1.a Go to project properties -> publish -> Application Files -> Check if there is any reference to this particular DLL other than GAC reference(by default this DLL would be reffered to DLL from GAC, when u explicitly add reference from your machine then the local references will also get added) -> If u find any such thing just exclude it build it again and trigger a new click once build -> the problem should be solved.
And for the reference set CopyLocal property to true. References -> Select the corresponding DLL -> Set copyLocal property to true.
Thanks,
Gayathri.
chand.gayu#gmail.com

C# Windows Forms Application Update on Application Startup

My application has been successfully updating for ages, and I've been making changes, releasing new builds etc every day for the past few months, but now, when the application starts (it checks for updates on startup), it begins downloading the updated version from the server, and then fails 3-quarters of the way through with the following message:
PLATFORM VERSION INFO Windows :
6.1.7600.0 (Win32NT) Common Language Runtime : 4.0.30319.1
System.Deployment.dll : 4.0.30319.1
(RTMRel.030319-0100) clr.dll :
4.0.30319.1 (RTMRel.030319-0100) dfdll.dll : 4.0.30319.1
(RTMRel.030319-0100) dfshim.dll :
4.0.31106.0 (Main.031106-0000)
SOURCES Deployment url :
file:///C:/Users/Jason/Desktop/OOM.appref-ms%7C
Server : Microsoft-IIS/7.0
X-Powered-By : ASP.NET Deployment Provider url :
http://www.website.net.au/software/updates/something/OOM.application
Application url :
http://www.website.net.au/software/updates/something/jusername/Application%20Files/OOM_2_0_0_8/OOM.exe.manifest
Server : Microsoft-IIS/7.0
X-Powered-By : ASP.NET
IDENTITIES Application Identity :
OOM.exe,
Version=2.0.0.8, Culture=neutral,
PublicKeyToken=38928ec70a12c5e6,
processorArchitecture=x86, type=win32
ERROR SUMMARY Below is a summary of
the errors, details of these errors
are listed later in the log. *
Activation of
C:\Users\Jason\Desktop\One Stop
Management.appref-ms| resulted in
exception. Following failure messages
were detected: + Downloading
http://www.website.net.au/software/updates/something/jusername/Application
Files/OOM_2_0_0_8/One
Stop Management.exe.config did not
succeed. + The remote server
returned an error: (404) Not Found.
COMPONENT STORE TRANSACTION FAILURE
SUMMARY No transaction error was
detected.
WARNINGS There were no warnings
during this operation.
OPERATION PROGRESS STATUS *
[18/02/2011 5:55:50 PM] : Activation
of C:\Users\Jason\Desktop\One Stop
Management.appref-ms| has started. *
[18/02/2011 5:55:50 PM] : Performing
necessary update check as specified by
the deployment. * [18/02/2011 5:55:51
PM] : Consuming new update. *
[18/02/2011 5:55:52 PM] : Installation
of the application has started. *
[18/02/2011 5:55:53 PM] : Processing
of application manifest has
successfully completed. * [18/02/2011
5:55:53 PM] : Found compatible runtime
version 4.0.30319. * [18/02/2011
5:55:53 PM] : Request of trust and
detection of platform is complete.
ERROR DETAILS Following errors were
detected during this operation. *
[18/02/2011 5:55:54 PM]
System.Deployment.Application.DeploymentDownloadException
(Unknown subtype)
- Downloading http://www.website.net.au/software/updates/something/jusername/Application
Files/OOM_2_0_0_8/One
Stop Management.exe.config did not
succeed.
- Source: System.Deployment
- Stack trace: at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem
next) at
System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at
System.Deployment.Application.FileDownloader.Download(SubscriptionState
subState) at
System.Deployment.Application.DownloadManager.DownloadDependencies(SubscriptionState
subState, AssemblyManifest
deployManifest, AssemblyManifest
appManifest, Uri sourceUriBase, String
targetDirectory, String group,
IDownloadNotification notification,
DownloadOptions options) at
System.Deployment.Application.ApplicationActivator.DownloadApplication(SubscriptionState
subState, ActivationDescription
actDesc, Int64 transactionId,
TempDirectory& downloadTemp) at
System.Deployment.Application.ApplicationActivator.InstallApplication(SubscriptionState&
subState, ActivationDescription
actDesc) at
System.Deployment.Application.ApplicationActivator.ConsumeUpdatedDeployment(SubscriptionState&
subState, ActivationDescription
actDesc) at
System.Deployment.Application.ApplicationActivator.PerformDeploymentUpdate(SubscriptionState&
subState, String& errorPageUrl) at
System.Deployment.Application.ApplicationActivator.ProcessOrFollowShortcut(String
shortcutFile, String& errorPageUrl,
TempFile& deployFile) at
System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri
activationUri, Boolean isShortcut,
String textualSubId, String
deploymentProviderUrlFromExtension,
BrowserSettings browserSettings,
String& errorPageUrl) at
System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object
state) --- Inner Exception ---
System.Net.WebException
- The remote server returned an error: (404) Not Found.
- Source: System
- Stack trace: at System.Net.HttpWebRequest.GetResponse()
at
System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem
next)
COMPONENT STORE TRANSACTION DETAILS
No transaction information is
available.
Okay, so that tells me that there is a file that was not found. But I have double-checked, several times, and the file is there.
Anybody know what causes this?
Any help at all is appreciated!

IIS won't serve up *.config files by default to protect web.config and various other ASP configuration files which usually contain connection strings and other sensitive information involved in running the site. To get around this for Click-Once deployments all files get a .deploy added to the end so a *.config would be automatically renamed *.config.deploy when published. Did you manually add One Stop Management.exe.config or something? You might add a .deploy on the end as a temp workaround but in reality this should have been done for you at publish time. You DON'T want enable configs to download from IIS as this will present a security hole with your site.

I recently solved this exact same problem.
We had an application that was at a x.y.z.14 version and we kept making tons of modifications to it to the point where it got up to x.y.z.33 before we released it to our end users. After releasing the live version a handful were unable to upgrade from x.y.z.14 because we had removed the folder for it in the Application Files directory in the ClickOnce deploy.
After using fiddler to see exactly what the HTTP requests were saying I realized that yes indeed the 404 not found error was created because that folder that people needed to update through to the x.y.z.33 and beyond version just wasn't there. The manifest file that is.
If this happens to you, hopefully you have a rollback that you can use to add the most recent base version of your application to 'jump start' to the new version.