cmd.exe crashes during .NET 3.5 package installation

I'm using the HowTo from DreadLion72 to install .NET package. The installation starts in a cmd box during the complete new installation of a new machine. The problem: the cmd.exe crashes during the .NET installation process. When I start the installation without cmd.exe, is everything ok. But my Software management tool (Empirum) needs to open cmd.exe to start the package installer.

Anybody knows why the cmd.exe crashes? Any idea for a solution?

0 Comments   [ + ] Show comments

Answers (3)

Posted by: AngelD 14 years ago
Red Belt
You should find any required info to troubleshoot .NET installations at http://blogs.msdn.com/astebner/articles/454956.aspx
Posted by: jmcfadyen 14 years ago
5th Degree Black Belt
.Net doesnt like installing without a user profile accessible.

I am guessing empirum is running as local system.

try running as user context to see if it works while logged on as both admin as user
Posted by: anonymous_9363 14 years ago
Red Belt
We've had no issues deploying all the .Net flavours as transformed MSIs via Group Policy. I recall we had some thrashing about to do with the transforms but nothing that isn't documented here.

my Software management tool (Empirum) needs to open cmd.exe to start the package installer. :-0 ! Great product, then. I hope you didn't have to pay much - if anything - for it.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login


This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ