[Bug 41727] rundll32.exe reports 'This application could not be started' during WINEPREFIX update with .NET Framework 4.0 installed only (unmanaged processes trigger legacy CLR 2.0 activation policy)

WineHQ Bugzilla wine-bugs at winehq.org
Wed May 6 15:39:57 CDT 2020


https://bugs.winehq.org/show_bug.cgi?id=41727

--- Comment #6 from Anastasius Focht <focht at gmx.net> ---
Hello folks,

in my previous comment #5, 'OnlyUseLatestCLR' setting was mentioned with "big
hammer/red knob" in the list of possible workarounds.

The potential danger/impact of this global setting is mentioned in this
StackOverflow thread:

https://stackoverflow.com/questions/2094694/how-can-i-run-powershell-with-the-net-4-runtime
("How can I run PowerShell with the .NET 4 runtime?")

--- quote ---
Please be VERY careful with using the registry key approach. These are
machine-wide keys and forcibily migrate ALL applications to .NET 4.0.

Many products do not work if forcibily migrated and this is a testing aid and
not a production quality mechanism. Visual Studio 2008 and 2010, MSBuild,
turbotax, and a host of websites, SharePoint and so on should not be
automigrated. 
--- quote ---

Providing 'rundll32.exe.config' would be an optimal solution with minimal
impact but Windows doesn't have this. Also by default Wine-Mono is
installed/used which doesn't require this mechanism at all.

Regards

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.



More information about the wine-bugs mailing list