none
Windows 7 claiming .NET 3.5 not installed RRS feed

  • Question

  • Dear All

    I have tried to install the Open XML SDK 2.0 on my development computer at work. When I try to do that, ithe instalation routine tells me that it cannot continue because .NET 3.5 is not installed. I have tried to uninstall the framework in the add remove windows features, and reinstall it, but still I get the mentioend error message.

    I can create and compile a .NET 3.5 project in Visual Studio 2010. I have a laptop for work with the same issue. When I try to install the SDK on my own private laptop, which is a x64 Windows 7 like my work PC's I can install it with no issues.

    My own private laptop is not part of a domain, but my work computers are. Is there any domain policies that might interfere with .NET 3.5 on Windows 7?

    Kind regards

    Tom Madsen

    Thursday, December 2, 2010 3:29 PM

Answers

  • Hi Tom Madsen,

     

    Thank you for reply.

    From your log file, I found some error information as follows.

    INFO   : [12/06/2010 09:35:42:957] [VsdLaunchConditions                     ]: Custom Action is starting...

    INFO   : [12/06/2010 09:35:42:958] [VsdLaunchConditions                     ]: CoInitializeEx - COM initialization Apartment Threaded...

    INFO   : [12/06/2010 09:35:42:958] [VsdLaunchConditions                     ]: Enumerating table using SQL statement: 'SELECT * FROM `_VsdLaunchCondition`'

    INFO   : [12/06/2010 09:35:42:959] [VsdLaunchConditions                     ]: Calling MsiGetActiveDatabase...

    INFO   : [12/06/2010 09:35:42:959] [VsdLaunchConditions                     ]: MsiDatabaseOpenViewW - Prepare Database to view table...

    INFO   : [12/06/2010 09:35:42:960] [VsdLaunchConditions                     ]: TMsiViewExecute - Open Database view on table...

    INFO   : [12/06/2010 09:35:42:960] [VsdLaunchConditions                     ]: Checking a launch condition...

    INFO   : [12/06/2010 09:35:42:961] [VsdLaunchConditions                     ]: Getting the condition to evaluate...

    INFO   : [12/06/2010 09:35:42:961] [VsdLaunchConditions                     ]: MsiRecordGetStringW - Fetching value...

    INFO   : [12/06/2010 09:35:42:961] [VsdLaunchConditions                     ]: MsiRecordGetStringW - Getting value from column '1'...

    INFO   : [12/06/2010 09:35:42:961] [VsdLaunchConditions                     ]: Evaluating condition 'VSDFXAvailable'...

    INFO   : [12/06/2010 09:35:42:962] [VsdLaunchConditions                     ]: RESULT:     Condition is true. Nothing more to do.

    INFO   : [12/06/2010 09:35:42:962] [VsdLaunchConditions                     ]: Checking a launch condition...

    INFO   : [12/06/2010 09:35:42:962] [VsdLaunchConditions                     ]: Getting the condition to evaluate...

    INFO   : [12/06/2010 09:35:42:962] [VsdLaunchConditions                     ]: MsiRecordGetStringW - Fetching value...

    INFO   : [12/06/2010 09:35:42:963] [VsdLaunchConditions                     ]: MsiRecordGetStringW - Getting value from column '1'...

    INFO   : [12/06/2010 09:35:42:963] [VsdLaunchConditions                     ]: Evaluating condition 'NETSPREGISTRYVALUE AND NETSPREGISTRYVALUE>="#1"'...

    INFO   : [12/06/2010 09:35:42:963] [VsdLaunchConditions                     ]: RESULT:     Condition is false.

    INFO   : [12/06/2010 09:35:42:963] [VsdLaunchConditions                     ]: MsiRecordGetStringW - Fetching value...

    INFO   : [12/06/2010 09:35:42:964] [VsdLaunchConditions                     ]: MsiRecordGetStringW - Getting value from column '2'...

    DEBUG: Error 2835:  The control ErrorIcon was not found on dialog ErrorDialog

    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2835. The arguments are: ErrorIcon, ErrorDialog,

    This setup requires the .NET Framework version 3.5 SP1. Please install the .NET Framework and run this setup again. The .NET Framework can be obtained from the web. Would you like to do this now?

    INFO   : [12/06/2010 09:35:45:833] [VsdLaunchConditions                     ]: MsiSetPropertyW - Setting Property Value...

    INFO   : [12/06/2010 09:35:45:834] [VsdLaunchConditions                     ]: MsiSetPropertyW - Setting property 'HideFatalErrorForm' to 'TRUE'.

    ERROR  : [12/06/2010 09:35:45:835] [VsdLaunchConditions                     ]: Custom Action failed with code: '1603'

    INFO   : [12/06/2010 09:35:45:835] [VsdLaunchConditions                     ]: Custom Action completed with return code: '1603'

    CustomAction VSDCA_VsdLaunchConditions returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

    Action ended 9:35:45: VSDCA_VsdLaunchConditions. Return value 3.

    Action ended 9:35:45: INSTALL. Return value 3.

     

    It is a condition to install this component that to check if HKLM\Software\Microsoft\NET Framework Setup\NDP\v3.5\SP should be >= 1.

    If .NET Framework was installed on WOW64 folder, please double check HKLM\Wow6432Node\Microsoft\NET Framework Setup\NDP\v3.5\SP should be >= 1.

     

    If you have any questions, please feel free to let me know.

    Best Regards,

    Larcolais

    Any update? Is your issue resolved?

    Best Regards,

    Larcolais


    MSDN Subscriber Support in Forum
    If you have any feedback of our support, please contact msdnmg@microsoft.com.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    • Marked as answer by Larcolais Gong Friday, December 10, 2010 10:44 AM
    Friday, December 10, 2010 2:10 AM

All replies

  • Can you precisely check the exact requirement of the applciation, ie whether it requires .net 3.5 or .net 3.5 sp1. 

     

    After that, check which version do you have installed. with windows 7, .net 3.5 SP1 is already installed that can be turned off using windows features

    http://social.msdn.microsoft.com/Forums/en-US/netfxsetup/thread/416f5dd6-34f2-4006-9adf-008720cf3f1a

     

    You can read this article on dealing with integral framework issues:

    http://blogs.msdn.com/b/astebner/archive/2007/03/26/how-to-repair-the-net-framework-2-0-and-3-0-on-windows-vista.aspx

    Note that Aaron Stebner links to the above for Win 7 integral .NET Framework issues:

    http://blogs.msdn.com/b/astebner/archive/2009/03/04/9459067.aspx


    mole on left eye
    Thursday, December 2, 2010 8:29 PM
  • The Open XML SDK 2.0 requires .NET 3.5 SP1, and this framework is installed with my Win 7 computers.

    I have tried to run the sfc /scannow recommednded in the blog post you suggested, but it does not come back with any issues after the scan. for some reason the setup process for the SDK does not recognize the installation of .NET 3.5 SP1.

    I am at my wits end...

    Regards

    Tom

    Friday, December 3, 2010 8:36 AM
  • Hi Tom Madsen,

    Thank you for posting.

    I downloaded OpenXMLSDK2 and OpenXMLSDKTool and installed them successfully one by one. (My OS is Windows 7 64bit)

    OpenXMLSDKTool MSI decides if it can be installed on your machine according two conditions. One is dependent on a registry’s key (HKLM\Software\Microsoft\NET Framework Setup\NDP\v3.5), another is need to check some properties or others about .NET Framework.

    So the error information “This setup requires the .NET Framework version 3.5 SP1. Please install the .NET Framework and run this setup again.” is thrown by MSI, not OS. I recommend that you can type the following command to get the installation log files and send it to me (v-xugong AT Microsoft.com) to help us analysis your issue.

    msiexec /i OpenXMLSDKv2.msi /log C:\Users\Desktop\myinstalllog.txt

    If you have any questions, please feel free to let me know.

    Best Regards,

    Larcolais


    MSDN Subscriber Support in Forum
    If you have any feedback of our support, please contact msdnmg@microsoft.com.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    Monday, December 6, 2010 8:24 AM
  • Hi Tom Madsen,

     

    Thank you for reply.

    From your log file, I found some error information as follows.

    INFO   : [12/06/2010 09:35:42:957] [VsdLaunchConditions                     ]: Custom Action is starting...

    INFO   : [12/06/2010 09:35:42:958] [VsdLaunchConditions                     ]: CoInitializeEx - COM initialization Apartment Threaded...

    INFO   : [12/06/2010 09:35:42:958] [VsdLaunchConditions                     ]: Enumerating table using SQL statement: 'SELECT * FROM `_VsdLaunchCondition`'

    INFO   : [12/06/2010 09:35:42:959] [VsdLaunchConditions                     ]: Calling MsiGetActiveDatabase...

    INFO   : [12/06/2010 09:35:42:959] [VsdLaunchConditions                     ]: MsiDatabaseOpenViewW - Prepare Database to view table...

    INFO   : [12/06/2010 09:35:42:960] [VsdLaunchConditions                     ]: TMsiViewExecute - Open Database view on table...

    INFO   : [12/06/2010 09:35:42:960] [VsdLaunchConditions                     ]: Checking a launch condition...

    INFO   : [12/06/2010 09:35:42:961] [VsdLaunchConditions                     ]: Getting the condition to evaluate...

    INFO   : [12/06/2010 09:35:42:961] [VsdLaunchConditions                     ]: MsiRecordGetStringW - Fetching value...

    INFO   : [12/06/2010 09:35:42:961] [VsdLaunchConditions                     ]: MsiRecordGetStringW - Getting value from column '1'...

    INFO   : [12/06/2010 09:35:42:961] [VsdLaunchConditions                     ]: Evaluating condition 'VSDFXAvailable'...

    INFO   : [12/06/2010 09:35:42:962] [VsdLaunchConditions                     ]: RESULT:     Condition is true. Nothing more to do.

    INFO   : [12/06/2010 09:35:42:962] [VsdLaunchConditions                     ]: Checking a launch condition...

    INFO   : [12/06/2010 09:35:42:962] [VsdLaunchConditions                     ]: Getting the condition to evaluate...

    INFO   : [12/06/2010 09:35:42:962] [VsdLaunchConditions                     ]: MsiRecordGetStringW - Fetching value...

    INFO   : [12/06/2010 09:35:42:963] [VsdLaunchConditions                     ]: MsiRecordGetStringW - Getting value from column '1'...

    INFO   : [12/06/2010 09:35:42:963] [VsdLaunchConditions                     ]: Evaluating condition 'NETSPREGISTRYVALUE AND NETSPREGISTRYVALUE>="#1"'...

    INFO   : [12/06/2010 09:35:42:963] [VsdLaunchConditions                     ]: RESULT:     Condition is false.

    INFO   : [12/06/2010 09:35:42:963] [VsdLaunchConditions                     ]: MsiRecordGetStringW - Fetching value...

    INFO   : [12/06/2010 09:35:42:964] [VsdLaunchConditions                     ]: MsiRecordGetStringW - Getting value from column '2'...

    DEBUG: Error 2835:  The control ErrorIcon was not found on dialog ErrorDialog

    The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2835. The arguments are: ErrorIcon, ErrorDialog,

    This setup requires the .NET Framework version 3.5 SP1. Please install the .NET Framework and run this setup again. The .NET Framework can be obtained from the web. Would you like to do this now?

    INFO   : [12/06/2010 09:35:45:833] [VsdLaunchConditions                     ]: MsiSetPropertyW - Setting Property Value...

    INFO   : [12/06/2010 09:35:45:834] [VsdLaunchConditions                     ]: MsiSetPropertyW - Setting property 'HideFatalErrorForm' to 'TRUE'.

    ERROR  : [12/06/2010 09:35:45:835] [VsdLaunchConditions                     ]: Custom Action failed with code: '1603'

    INFO   : [12/06/2010 09:35:45:835] [VsdLaunchConditions                     ]: Custom Action completed with return code: '1603'

    CustomAction VSDCA_VsdLaunchConditions returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

    Action ended 9:35:45: VSDCA_VsdLaunchConditions. Return value 3.

    Action ended 9:35:45: INSTALL. Return value 3.

     

    It is a condition to install this component that to check if HKLM\Software\Microsoft\NET Framework Setup\NDP\v3.5\SP should be >= 1.

    If .NET Framework was installed on WOW64 folder, please double check HKLM\Wow6432Node\Microsoft\NET Framework Setup\NDP\v3.5\SP should be >= 1.

     

    If you have any questions, please feel free to let me know.

    Best Regards,

    Larcolais

    Any update? Is your issue resolved?

    Best Regards,

    Larcolais


    MSDN Subscriber Support in Forum
    If you have any feedback of our support, please contact msdnmg@microsoft.com.
    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
    • Marked as answer by Larcolais Gong Friday, December 10, 2010 10:44 AM
    Friday, December 10, 2010 2:10 AM
  • I had a similar issue with the MSI indicating a framework component was missing (when it was actually installed). 

    Running msiexec from an administrator command prompt allowed the installation to continue without error.

    Wednesday, January 19, 2011 10:48 PM
  • Thanks! This resolved my issue :-)
    Tuesday, March 15, 2011 1:02 PM
  • Its hard to believe that this issue has still not been fixed. Today (10/12/2011) I tried to download the OpenXMLSDKv2.msi and tried to install it on my dev win7 box. Right clicked and run as admin. Gives and error .net 3.5 Sp1 is not installed. I was not aware .net 3.5 is a windows7 feature/component. I downloaded 3.5 SP1 and tried to run it and it gave me the same error - go and turn this from windows feature on and off. It just did not make sense. After wasting 1.5 hrs I luckily landed on this thread. As the above user wrote. Goto Start->find cmd->right click and run as admin. Now from the CMD run the OpenXML SDKv2 msi.
    • Proposed as answer by jaberma3 Monday, April 16, 2012 7:06 PM
    Wednesday, October 12, 2011 9:08 PM
  • Thanks a ton!!!! Performing the install using msicexec solved my problem as well. I was unable to install HPC Pack Client Utilities on Windows 7 and was going nuts. I tried uninstalling and installling .NET Framework 3.5 SP1 but did not help, this was the only solution that was a life saver. Thanks again!

    Monday, December 12, 2011 11:53 PM
  • I have the same error on my log.  However, the fix does not work for me.  I have Server 2008 R2 64-bit.

    Other people recommendation to run from the command (run as administrator) and msiexec does not work for me either. 

    Any recommendation or suggestion is greatly appreciated.

    One correction note to your post:

    If .NET Framework was installed on WOW64 folder, please double check HKLM\Wow6432Node\Microsoft\NET Framework Setup\NDP\v3.5\SP should be >=1  <--- should be HKLM\Software\Wow6432Node\Microsoft\NET Framework Setup\NDP\v3.5\SP should be >=1

     

    Wednesday, December 14, 2011 11:28 PM
  • I had the same problem on my Windows 7 64-bit machine. Running msiexec from an administrator command prompt also worked for me.

    Thanks!

    Rich


    Rich Stewart

    Tuesday, June 5, 2012 8:11 PM