Apps that never needed it, now suddenly ask for NetFX 3.5...

Discussion in 'Windows 10' started by MonarchX, Aug 11, 2018.

  1. MonarchX

    MonarchX MDL Expert

    May 5, 2007
    1,732
    313
    60
    For example, I know CrazyBump program never needed NetFX 3.5 to be installed to run, but ever since June updates many Apps that never needed NetFX 3.5 ask for it, even with the "Use the latest NET Framework version" tweak enabled... I'm on Windows 10 LTSB.

    What gives? I don't want to that installed when I know its not needed... If that's due to Windows 10 July updates, then the issue should have been resolved with the latest CU, which I have applied, but that obviously did not do the trick...
     
  2. Katsuobushi

    Katsuobushi Guest

    #2 Katsuobushi, Aug 11, 2018
    Last edited by a moderator: Aug 11, 2018
    del
     
  3. WindowsGeek

    WindowsGeek MDL Expert

    Jun 30, 2015
    1,462
    420
    60
    Maybe does apps require that now to run.
     
  4. KaoDome

    KaoDome MDL Novice

    Jul 31, 2009
    35
    13
    0
    Depending on the program you may be able to run it with .NET 4+ by having a config file alongside its executable (or editing it if it's already present).

    The name follows this pattern:
    Code:
    Program.exe
    Program.exe.config
    It's an XML formatted file and I think this would be the minimum .NET 4:
    Code:
    <?xml version="1.0"?>
    <configuration>
      <startup useLegacyV2RuntimeActivationPolicy="true">
        <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0,Profile=Client"/>
      </startup>
    </configuration>
    
    It could also be useful to add these lines as well if it doesn't work with just the above lines:
    Code:
      <runtime>
        <legacyCorruptedStateExceptionsPolicy enabled="true"/>
        <loadFromRemoteSources enabled="true"/>
      </runtime>
    
    The runtime element goes under configuration same as startup:
    Code:
    <?xml version="1.0"?>
    <configuration>
      <runtime>
        ...
      </runtime>
      <startup>
        ...
      </startup>
    </configuration>
    
    This is per app, not a system-wide solution but may be helpful to you.