Installation error on windows 7

Dec 16, 2009 at 7:52 PM

I cant install this new DroidExplorer.0.8.2.1.x64 on Windows 7 anymore.. it claims I dont have .net framework 3.5 sp1.. (wich actully comes with win7) old versions worked fine..

 

Dec 19, 2009 at 9:37 PM

I have the same problem.. Previous version worked fine. And Im 100% sure that 3.5 sp1 is already installled (It is not possible reinstall).

(Using windows 7 x64)

Dec 19, 2009 at 9:46 PM

Solved it. Installed .net 4.0 beta. Installed droid and then uninstalled .net 4.0 since droid crash with it. And droid will still work.

Den dec 19, 2009 10:37 em, "tjatte" <notifications@codeplex.com> skrev:

From: tjatte

I have the same problem.. Previous version worked fine. And Im 100% sure that 3.5 sp1 is already installled (It is not possible reinstall).

(Using windows 7 x64)

Read the full discussion online. To add a post to this discussion, reply to this email (de@discus...

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com

Dec 20, 2009 at 9:54 AM

Same problem on Windows 7 Enterprise (x86). I cannot install the .NET 4 beta on this machine, so that fix is a no-go. Please fix this installation issue.

Coordinator
Dec 22, 2009 at 1:35 PM

Are you using a RC or Beta of windows 7? because I have retail windows 7 x64 RTM  and windows 7 x86 RTM and I have droid explorer installed on both machines. I do not have .net 4.0 installed on either of them. I am asking because I am trying to track this issue down. The code is checking the registry to see if .net 3.5 sp1 is installed, that is how it determines if it is. I have had confirmation from a number of other people running windows 7 that it does indeed install. Any additional information you can provide me with would be helpful. also if you could try installing again from the command line with the /log switch added, and post the log files here on codeplex. You will probably have to post them under the issue tracker. Thank you.

Coordinator
Dec 22, 2009 at 1:39 PM

could you also check in the registry and look if SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\ exists. if it does, is there a value, named "SP" with a value >= 1?

Dec 22, 2009 at 2:46 PM

Ok, here's the log output:

 

2009-12-22 15:28:26,820 [1    ] [INFO ] [DroidExplorer.Bootstrapper.Program] System Info: Microsoft Windows NT 6.1.7600.0 x64
2009-12-22 15:28:26,836 [1    ] [DEBUG] [DroidExplorer.Bootstrapper.Program] Starting setup with arguments: /log
2009-12-22 15:28:26,838 [1    ] [DEBUG] [DroidExplorer.Bootstrapper.Program] Mode set to install
2009-12-22 15:28:26,839 [1    ] [DEBUG] [DroidExplorer.Bootstrapper.Program] Checking for Minimum .net version
2009-12-22 15:28:26,842 [1    ] [FATAL] [DroidExplorer.Bootstrapper.Program] The requirement of .net framework 3.5 SP 1 was not found.

 

 

2009-12-22 15:28:26,820 [1    ] [INFO ] [DroidExplorer.Bootstrapper.Program] System Info: Microsoft Windows NT 6.1.7600.0 x64

2009-12-22 15:28:26,836 [1    ] [DEBUG] [DroidExplorer.Bootstrapper.Program] Starting setup with arguments: /log

2009-12-22 15:28:26,838 [1    ] [DEBUG] [DroidExplorer.Bootstrapper.Program] Mode set to install

2009-12-22 15:28:26,839 [1    ] [DEBUG] [DroidExplorer.Bootstrapper.Program] Checking for Minimum .net version

2009-12-22 15:28:26,842 [1    ] [FATAL] [DroidExplorer.Bootstrapper.Program] The requirement of .net framework 3.5 SP 1 was not found.

 

 

 

This is true for me: SOFTWARE\Microsoft\NET Framework Setup\NDP\v3.5\ exists. if it does, is there a value, named "SP" with a value >= 1?

I have English Windows 7 x64 Ultimate retail RTM

I've also installed Visual Studio Express 2008, SQL server express 2008 and MS ASP.NET MVC 1.0 if those are making the detection problem.

What you COULD do is to release a x64 version without the .NET check until you find a solution. (Let's call it the Window 7 x64 version because it won't need a check)

Thanks for a otherwise great software!

 

Coordinator
Dec 22, 2009 at 4:05 PM

Ok, looking at your post, I think I know what the issue is. The installer is an x86 binary, so it actually ends up looking in HKLM\SOFTWARE\WOW6432Node\Microsoft\NET Framework Setup\NDP\v3.5\.

I don't know why this "got past" me. The installer needs to be x86 in order to check for other components. I should have a new version up before the end of the week. If you cant wait that long, a "hack" would be to create the HKLM\SOFTWARE\WOW6432Node\Microsoft\NET Framework Setup\NDP\v3.5\ registry entry for install, then you can delete the key after.

I will probably change the way it checks for .net 3.5sp1. Unless I can find a way to check the x64 tree from x86, which I dont think I can.

Dec 22, 2009 at 4:33 PM
Hmm, ok.

After looking in the registry I would say that "the hack" was already in place to begin with somehow and that didn't help...

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v3.5]
"Version"="3.5.30729.4926"
"CBS"=dword:00000001
"Install"=dword:00000001
"InstallPath"="C:\\Windows\\Microsoft.NET\\Framework\\v3.5\\"
"SP"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v3.5\1033]
"Version"="3.5.30729.4926"
"CBS"=dword:00000001
"Install"=dword:00000001
"SP"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\NET Framework Setup\NDP\v3.5\1053]
"Version"="3.5.30729.4926"
"CBS"=dword:00000001
"Install"=dword:00000001
"SP"=dword:00000001 

2009/12/22 camalot <notifications@codeplex.com>

From: camalot

Ok, looking at your post, I think I know what the issue is. The installer is an x86 binary, so it actually ends up looking in HKLM\SOFTWARE\WOW6432Node\Microsoft\NET Framework Setup\NDP\v3.5\.

I don't know why this "got past" me. The installer needs to be x86 in order to check for other components. I should have a new version up before the end of the week. If you cant wait that long, a "hack" would be to create the HKLM\SOFTWARE\WOW6432Node\Microsoft\NET Framework Setup\NDP\v3.5\ registry entry for install, then you can delete the key after.

I will probably change the way it checks for .net 3.5sp1. Unless I can find a way to check the x64 tree from x86, which I dont think I can.

Read the full discussion online.

To add a post to this discussion, reply to this email (de@discussions.codeplex.com)

To start a new discussion for this project, email de@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com





Coordinator
Dec 22, 2009 at 6:26 PM

hmm, ok, thanks. once I get home, I can dig in to it more, i have an win7 x64 machine to test with.