http://bugs.winehq.org/show_bug.cgi?id=34803
Bug #: 34803 Summary: .NET Framework 2.0 SP2 refuses to install on top of .NET 2.0 SP1 (SBSDisabled registry key install blocker detected) Product: Wine Version: 1.7.5 Platform: x86 OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: focht@gmx.net Classification: Unclassified
Hello folks,
some users reported this in Wine appdb entry for .NET Framework 2.0:
--- quote --- I can't .NET Framework 2.0 SP2 install 2.0 basic and SP1 its going normally, only have I problem SP2
Log: err:msi:ITERATE_Actions Execution halted, action L"DD_CA_InstallBlock_X86.3643236F_FC70_11D3_A536_0090278A1BB8" returned 1603 fixme:imm:ImmDisableIME (-1): stub err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded err:ole:CoInitializeEx Attempt to change threading model of this apartment from multi-threaded to apartment threaded
I searched here this solution, but i find not my Linux: Ubunt 12.04 LTS --- quote ---
--- quote --- I also am getting the same error but on ubuntu 13.10 and using
$ wine --version wine-1.7.4 --- quote ---
Indeed, .NET Framework 2.0 SP2 installer refuses to install on top of .NET Framework 2.0 SP1.
Relevant part of trace log:
--- snip --- ... 002f:trace:msi:ACTION_AppSearchReg L"SearchInstallBlock_____X86.3643236F_FC70_11D3_A536_0090278A1BB8" ... 002f:Call advapi32.RegOpenKeyW(80000002,00187208 L"SOFTWARE\Microsoft\.NETFramework\v2.0.50727\SBSDisabled",007ce548) ret=7dac04b9 002f:trace:reg:NtOpenKey (0x18,L"SOFTWARE\Microsoft\.NETFramework\v2.0.50727\SBSDisabled",2000000,0x7ce548) 002f:trace:reg:NtOpenKey <- 0xc8 002f:Ret advapi32.RegOpenKeyW() retval=00000000 ret=7dac04b9 ... 002f:Call advapi32.RegQueryValueExW(000000c8,00186ff0 L"Install",00000000,00000000,00000000,007ce544) ret=7dac0574 002f:trace:reg:RegQueryValueExW (0xc8,L"Install",(nil),(nil),(nil),0x7ce544=0) 002f:trace:reg:NtQueryValueKey (0xc8,L"Install",2,0x7ce380,12) 002f:Ret advapi32.RegQueryValueExW() retval=00000000 ret=7dac0574 ... 002f:trace:msi:msi_set_property 0x1650c0 L"DD_INSTALLBLOCKFOUND_X86.3643236F_FC70_11D3_A536_0090278A1BB8" L"1" -1 ... 002f:trace:msi:MSI_EvaluateConditionW L"( (NOT REMOVE) AND DD_INSTALLBLOCKFOUND_X86.3643236F_FC70_11D3_A536_0090278A1BB8 )" ... 002f:trace:msi:MSI_EvaluateConditionW 1 <- L"( (NOT REMOVE) AND DD_INSTALLBLOCKFOUND_X86.3643236F_FC70_11D3_A536_0090278A1BB8 )" 002f:trace:msi:ACTION_PerformAction Performing action (L"DD_CA_InstallBlock_X86.3643236F_FC70_11D3_A536_0090278A1BB8") ... 002f:trace:msi:ACTION_CustomAction Handling custom action L"DD_CA_InstallBlock_X86.3643236F_FC70_11D3_A536_0090278A1BB8" (13 (null) L"Setup cannot continue because this version of the .NET Framework is incompatible with a previously installed one. For more information, see http://support.microsoft.com/support/kb/articles/q312/5/00.asp") ... 002f:err:msi:ITERATE_Actions Execution halted, action L"DD_CA_InstallBlock_X86.3643236F_FC70_11D3_A536_0090278A1BB8" returned 1603 ... --- snip ---
The "SBSDisabled" -> "Install=1" key prevents this.
There are many MS KB and blog entries about .NET installers/updates refusing to install/uninstall in certain combinations so this might be even a limitation on Windows.
Though installing
.NET Framework 2.0 SP2 on top of .NET Framework 2.0 .NET Framework 2.0 SP2 on top of .NET Framework 3.5
works.
The installation can be forced by removing the key:
--- snip --- $ wine reg delete "HKLM\SOFTWARE\Microsoft\.NETFramework\v2.0.50727\SBSDisabled" --- snip ---
Using the .NET Framework Setup Verification Tool from Aaron Stebner (Microsoft) which checks for proper installation of .NET assemblies and registry entries one can indeed see the forced installation of SP2 on top of SP1 was not proper: the test application crashes.
Website and download here: http://blogs.msdn.com/b/astebner/archive/2008/10/13/8999004.aspx
.NET 2.0 SP1 and .NET 2.0 SP2 are validated successfully with the tool if they are installed independently on top of .NET 2.0
So this installer block might be really a valid limitation.
Maybe someone with a pristine Windows 2000/XP install (no .NET service packs) could try to install this combination: 2.0 SP1 + 2.0 SP2 and check if it exhibits the same error.
Regards