I'm deploying KeePass MSI via Microsoft SCCM to Windows 10 1607 for the first time. at first it wouldn't let me install it unless I used the /qb msiexec switch. which, ok, weird, but I can deal with that. It still won't install because now it claims that it needs .NET 3.5 which Win10 doesn't have. I've searched through the forums and I've seen posts that says KeePass should work fine on .NET 4.X which is great, but then how do I suppress this check for .NET 3.5
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yeah, but if it does work with 4.X, I'd like to leave off 3.5 if possible since it's not in there by default.
It just depends. This is literally the first app I've tested on Win10 and it just stood out because it deploys to our Win7 boxes automatically but it failed on our Win10 test machines, if we run into more apps that are dependent on 3.5, then yeah, I suspect we'll just add 3.5 to Win10.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I attempted to install it just now. still need to do the /qb switch in order to get it to run, but I then get a prompt that says "The specified account already exists"
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for the late response, but I just tried installing the new file. The initial prompt is gone (and I also didn't need the /qb switch this time) but then the installer moves on to copying the files. After the files are copied, the prompt to download and install 3.5 comes back. When I hit no, the installer rolls everything back.
Last edit: Tim Menke 2016-08-22
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm out of ideas, sorry. The setup now should accept any .NET Framework, and all prerequisites have been removed; I don't know why you're still getting the .NET 3.5 prompt.
I'm deploying KeePass MSI via Microsoft SCCM to Windows 10 1607 for the first time. at first it wouldn't let me install it unless I used the /qb msiexec switch. which, ok, weird, but I can deal with that. It still won't install because now it claims that it needs .NET 3.5 which Win10 doesn't have. I've searched through the forums and I've seen posts that says KeePass should work fine on .NET 4.X which is great, but then how do I suppress this check for .NET 3.5
Thanks!
Win 10 also has .NET 3.5
If you add it in the Windows features dialog.
Yeah, but if it does work with 4.X, I'd like to leave off 3.5 if possible since it's not in there by default.
It just depends. This is literally the first app I've tested on Win10 and it just stood out because it deploys to our Win7 boxes automatically but it failed on our Win10 test machines, if we run into more apps that are dependent on 3.5, then yeah, I suspect we'll just add 3.5 to Win10.
I'm assuming there is a dependency in the MSI tables. Using InstEdit should allow you to modify the table to allow .NET 4.
http://www.instedit.com/
cheers, Paul
I've now changed the MSI to require any .NET Framework version, not 3.5 specifically.
Here's a MSI (repackaged KeePass 2.34) for testing:
http://keepass.info/filepool/KeePass-2.34.1.msi
Thanks and best regards,
Dominik
Thanks!
I attempted to install it just now. still need to do the /qb switch in order to get it to run, but I then get a prompt that says "The specified account already exists"
Maybe the installer is confused as there now are two different packages with the same version.
Please try the following:
http://keepass.info/filepool/KeePass-2.34.2.msi
(this again is KeePass 2.34 repackaged, but now with a different MSI version and product code).
Thanks and best regards,
Dominik
Sorry for the late response, but I just tried installing the new file. The initial prompt is gone (and I also didn't need the /qb switch this time) but then the installer moves on to copying the files. After the files are copied, the prompt to download and install 3.5 comes back. When I hit no, the installer rolls everything back.
Last edit: Tim Menke 2016-08-22
I'm out of ideas, sorry. The setup now should accept any .NET Framework, and all prerequisites have been removed; I don't know why you're still getting the .NET 3.5 prompt.
If anyone wants to have a look, here's the current VDPROJ file for building the MSI (with Visual Studio 2015):
http://keepass.info/filepool/KeePass_160824_msi.zip
Best regards,
Dominik