[Bug 10601] New: .NET Framework 2.0: Installation Fails

http://bugs.winehq.org/show_bug.cgi?id=10601

Summary: .NET Framework 2.0: Installation Fails
           Product: Wine
           Version: 0.9.49.
          Platform: PC
               URL: http://www.microsoft.com/downloads/details.aspx?familyid
                    =0856eacb-4362-4b0d-8edd-aab15c5e04f5&displaylang=en
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: wine-ole
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Created an attachment (id=9399)
 --> (http://bugs.winehq.org/attachment.cgi?id=9399)
wine console output

The installation appears to start correctly, but it eventually causes and
unhandled exception within wine.  I have installed IE6 as a prequisite.

[Bug 10601] .NET Framework 2.0: Installation Fails

http://bugs.winehq.org/show_bug.cgi?id=10601

James McKenzie  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from James McKenzie   2007-12-08 21:11:00 ---
This also occurs with 0.9.50 on Mac OS X 10.4
Attempting to find where a successful install happened and follow instructions
from there.

[Bug 10601] .NET Framework 2.0: Installation Fails

http://bugs.winehq.org/show_bug.cgi?id=10601

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |10787

[Bug 10601] .NET Framework 2.0: Installation Fails

http://bugs.winehq.org/show_bug.cgi?id=10601

Vitaliy Margolen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #2 from Vitaliy Margolen   2007-12-29 16:10:10 ---
*** Bug 10945 has been marked as a duplicate of this bug. ***

[Bug 10601] .NET Framework 2.0: Installation Fails

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #3 from James McKenzie   2007-12-29 17:15:46 ---
As a suggestion, use ps -aux to find the running installer and then kill -9 (or
kill -KILL) pid, where pid is the process id for the installer process.  I've
done this quite a few times to stop run-away processes under both Linux and Mac
OS X.

[Bug 10601] .NET Framework 2.0: Installation Fails

http://bugs.winehq.org/show_bug.cgi?id=10601

James Hawkins  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #4 from James Hawkins   2008-03-13 16:20:13 ---
*** Bug 12024 has been marked as a duplicate of this bug. ***

[Bug 10601] .NET Framework 2.0: Installation Fails

http://bugs.winehq.org/show_bug.cgi?id=10601

Dotan Cohen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1

--- Comment #5 from Dotan Cohen   2008-03-13 17:18:09 ---
*** This bug has been confirmed by popular vote. ***

[Bug 10601] .NET Framework 2.0: Installation Fails

http://bugs.winehq.org/show_bug.cgi?id=10601

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #6 from Anastasius Focht   2008-03-14 04:57:05 ---
Hello,

I don't see the point of leaving this bug in open state.

There are other bug reports where I documented the issues/fixes regarding
installation of .NET Framework versions and running .NET apps on top of it in
more detail.
The installation crashes should have been fixed.

Most people seem to be happy that installers say "successful" but technically
this isn't necessarily true.
Important steps (msi) are left out which later cause showstoppers to apps.

Either reformulate bugs like this and state the *exact* problem or close it.
If it crashes for you, provide more info.
Make sure you searched bugzilla/appdb before and use recent wine version.

Regards

[Bug 10601] .NET Framework 2.0: Installation Fails

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #7 from Dotan Cohen   2008-03-14 05:10:38 ---
@Anastasius:
This bug should stay open because .NET does not install by the standard
installation method. There may be hacks, workarounds, and fixes, but that does
not mean that the bug is fixed. And I personally did file a bug report with
lots of info, console output, and screenshots of the *exact* problem and error
messages. It was marked a dupe of this one, even though it is slightly
different (different errors).

When .NET can be installed by running $ wine dotnet2.0.exe and clicking your
way through it, then the bug will be fixed.

[Bug 10601] .NET Framework 2.0: Installation Fails

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #8 from Anastasius Focht   2008-03-14 09:29:29 ---
Hello,

--- quote ---
..
And I personally did file a bug report with
lots of info, console output, and screenshots of the *exact* problem and error
messages. It was marked a dupe of this one, even though it is slightly
different (different errors).

When .NET can be installed by running $ wine dotnet2.0.exe and clicking your
way through it, then the bug will be fixed.
--- quote ---

I retested with 0.9.55 and 0.9.57
Although there were some exceptions (expected due to wine deficiencies) the
overall installation result was "successful".

The official one from Micro$oft is usually named "dotnetfx.exe" and not
"dotnet2.0.exe".
Provide some official download location for that "dotnet2.0.exe" or verify it's
really the official one (date, checksum should match!).

- use 0.9.57 or later if possible (although it should work with 0.9.55 too)
- use clean .wine
- make sure your media source (cd/dvd whatever) is not corrupt
..

If the error persists with clean .wine, attach +tid,+seh,+relay,+msi logfile
here ... otherwise don't waste people's time.

Regards

[Bug 10601] .NET Framework 2.0: Installation Fails

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #9 from Dotan Cohen   2008-03-14 11:00:20 ---
Thank you Anastasius. I should have specified that it was with a clean ~/.wine.
I now see that I need IE installed first, so tell me before I test, would it be
preferable to install IE first, or install on a really, really, clean ~/.wine?

Also, I renamed the dotnetfx.exe file for my self, so that I would know what it
was. The file was obtained from a Microsoft download site. I can MD5 or SHA1 it
if you want, but it is the same file, only renamed for my convenience.

After I retest, I will update my original bug and if need be, undupe it. I will
update to 0.9.57 now, but I await your response regarding whether or not to
install IE before installing .NET. Thank you.

[Bug 10601] .NET Framework 2.0: Installation Fails

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #10 from Anastasius Focht   2008-03-14 11:40:35 ---
Hello,

--- quote ---
but I await your response regarding whether or not to
install IE before installing .NET. Thank you.
--- quote ---

The .NET 2.0 installer alone doesn't require any of the IE tricks nor
mozilla/gecko engine to be present.
Just execute it on clean ~/.wine and if the installer says "failed" attach the
compressed +tid,+seh,+relay,+msi log.

Regards

[Bug 10601] .NET Framework 2.0: Installation Fails

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #11 from Dotan Cohen   2008-03-14 20:02:24 ---
Anastasius, .NET installed with Wine 0.9.57. I congratulate the entire wine
team on the remarkable progress (two releases per month!) and I apologize for
filing a bug on an older version of the software without testing the latest
version first.

[Bug 10601] .NET Framework 2.0: Installation Fails

http://bugs.winehq.org/show_bug.cgi?id=10601

Louis Lenders  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #12 from Louis Lenders   2008-03-25 14:46:22 ---
Hmm, in current git the dotnet2.0 installer is failing again for me? Could
somebody else try to see if this is a problem on my side? It worked fine a
couple of weeks ago.....

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

Louis Lenders  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|.NET Framework 2.0:         |.NET Framework 2.0:
                   |Installation Fails          |Installation Fails in winxp
                   |                            |mode

--- Comment #13 from Louis Lenders   2008-03-25 14:48:54 ---
aha, seems related to version setting to winXP. When i set it back to win2k, it
goes fine again.

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #14 from Anastasius Focht   2008-03-25 15:10:47 ---
Hello,

--- snip ---
aha, seems related to version setting to winXP. When i set it back to win2k, it
goes fine again.
--- snip ---

Sorry I probably forgot to mention this now that wine has "Windows XP" as
default.
I described the problem a while ago somewhere between other .NET 2.0 bugs ;-)
The cause are reparse/junction point APIs which wine doesn't support/implement
yet.

Regards

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #15 from Anastasius Focht   2008-03-29 06:19:18 ---
Hello,

if you want to use default "Windows XP" config for .NET 2.0 installers there
are two ways to get it work.

The .NET 2.0 Framework installer checks if the target volume is NTFS filesystem
type and then uses the FSCTL_SET_REPARSE_POINT ioctl (used for mount points and
junctions) to create junction points for each registered assembly in Windows
SxS directory to GAC assembly directory (link target). 
Basically the junction point is used to redirect access from one directory to
another.

--- trace ---
0033:Call KERNEL32.GetVolumeInformationW(7eb5e3d4
L"C:\",00000000,00000000,00000000,7eb5e1c4,7eb5e1c4,7eb5e1c8,00000104)
ret=7a13f5bc
0033:trace:vxd:DeviceIoControl
(0x284,24000,(nil),0,0x7eb5ddb2,804,0x7eb5e0e8,(nil))
0033:Ret  KERNEL32.GetVolumeInformationW() retval=00000001 ret=7a13f5bc 
--- trace ---

I first thought they would look at the returned filesystem flags field (flags &
FILE_SUPPORTS_REPARSE_POINTS) - but that's not the case.
Instead they look directly at returned filesystem name string and compare it to
"NTFS".
Junction points were introduced with NTFS v3.0 - Windows 2000 and later.
There is a check for windows version >= Windows 2000 so NT4 NTFS 2.x targets
won't get junctions requests.

The quick fix is to not pretend that target is NTFS volume (fall back to
FAT32):

--- snip dlls/kernel32/volume.c ---

diff --git a/dlls/kernel32/volume.c b/dlls/kernel32/volume.c
index 74397a9..5c78fbd 100644
--- a/dlls/kernel32/volume.c
+++ b/dlls/kernel32/volume.c
@@ -619,7 +619,7 @@ fill_fs_info:  /* now fill in the information that depends
on the file system ty
         if (flags) *flags = FILE_CASE_PRESERVED_NAMES;  /* FIXME */
         break;
     default:
-        if (fsname) lstrcpynW( fsname, ntfsW, fsname_len );
+        if (fsname) lstrcpynW( fsname, fat32W, fsname_len );
         if (filename_len) *filename_len = 255;
         if (flags) *flags = FILE_CASE_PRESERVED_NAMES;
         break;

--- snip dlls/kernel32/volume.c ---

The long one: add NTFS junction support to wine (boils down to creation of *nix
symlink).

--- snip ---
0049:Call KERNEL32.CreateFileW(7e9fd2fc
L"C:\windows\assembly\GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a",c0000000,00000003,00000000,00000003,02200000,00000000)
ret=79ea0464
0049:Ret  KERNEL32.CreateFileW() retval=0000028c ret=79ea0464
0049:Call KERNEL32.lstrlenW(7e9fbfe4
L"C:\windows\WinSxS\x86_System.EnterpriseServices_b03f5f7f11d50a3a_2.0.0.0_x-ww_7d5f3790")
ret=7a13f794
0049:Ret  KERNEL32.lstrlenW() retval=00000056 ret=7a13f794
0049:Call KERNEL32.lstrlenW(7e9fbdd8
L"\??\C:\windows\WinSxS\x86_System.EnterpriseServices_b03f5f7f11d50a3a_2.0.0.0_x-ww_7d5f3790")
ret=7a13f79e
0049:Ret  KERNEL32.lstrlenW() retval=0000005a ret=7a13f79e
0049:Call KERNEL32.GetLastError() ret=79e85f0a
0049:Ret  KERNEL32.GetLastError() retval=00000000 ret=79e85f0a
0049:Call ntdll.RtlAllocateHeap(00110000,00000000,00000174) ret=79e78360
0049:Ret  ntdll.RtlAllocateHeap() retval=00d38dc0 ret=79e78360
0049:Call
KERNEL32.DeviceIoControl(0000028c,000900a4,00d38dc0,00000174,00000000,00000000,7e9fbdc4,00000000)
ret=7a13f846
0049:fixme:ntdll:server_ioctl_file Unsupported ioctl 900a4 (device=9 access=0
func=29 method=0)
0049:Ret  KERNEL32.DeviceIoControl() retval=00000000 ret=7a13f846
0049:Call KERNEL32.GetLastError() ret=7a13f856
0049:Ret  KERNEL32.GetLastError() retval=00000032 ret=7a13f856
--- snip ---

"\??\C:\windows\WinSxS\x86_System.EnterpriseServices_b03f5f7f11d50a3a_2.0.0.0_x-ww_7d5f3790"
is the native name for the junction.

"C:\windows\assembly\GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a"
is the redirect (link) target

My first approach was to stub FSCTL_SET_REPARSE_POINT in
ntdll.NtFsControlFile() (like FSCTL_LOCK_VOLUME) but this was not enough.

NOTE: the wine definitions of FSCTL_SET_REPARSE_POINT and
FSCTL_DELETE_REPARSE_POINT are incorrect or at least not valid for W2K, XP and
later.
Access type has to be FILE_ANY_ACCESS (0) when building the ioctl code.
E.g.: #define FSCTL_SET_REPARSE_POINT CTL_CODE(FILE_DEVICE_FILE_SYSTEM, 41,
METHOD_BUFFERED, FILE_ANY_ACCESS) -> 0x900a4

--- snip ---
0033:Call
KERNEL32.DeviceIoControl(00000284,000900a4,00d3b180,00000174,00000000,00000000,7eb5ddc4,00000000)
ret=7a13f846
0033:trace:vxd:DeviceIoControl
(0x284,900a4,0xd3b180,372,(nil),0,0x7eb5ddc4,(nil))
0033:fixme:ntdll:NtFsControlFile stub! return success - Unsupported fsctl 900a4
(device=9 access=0 func=29 method=0)
0033:Ret  KERNEL32.DeviceIoControl() retval=00000001 ret=7a13f846
0033:Call KERNEL32.CloseHandle(00000284) ret=7a13f7ca
0033:Ret  KERNEL32.CloseHandle() retval=00000001 ret=7a13f7ca
0033:Call KERNEL32.GetLastError() ret=79e782be
0033:Ret  KERNEL32.GetLastError() retval=00000000 ret=79e782be
..
0033:Call KERNEL32.lstrlenW(00d3a4f8
L"C:\windows\assembly\GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a")
ret=79f6d793
0033:Ret  KERNEL32.lstrlenW() retval=0000004e ret=79f6d793
0033:Call shlwapi.PathAddBackslashW(00d3a4f8
L"C:\windows\assembly\GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a")
ret=79f6d7a9
0033:Ret  shlwapi.PathAddBackslashW() retval=00d3a596 ret=79f6d7a9
0033:Call KERNEL32.GetFileAttributesExW(00d3a730
L"C:\windows\assembly\GAC_32\System.EnterpriseServices\2.0.0.0__b03f5f7f11d50a3a\System.EnterpriseServices.dll",00000000,7eb5e82c)
ret=7a143d7c
0033:Ret  KERNEL32.GetFileAttributesExW() retval=00000000 ret=7a143d7c
0033:Call KERNEL32.GetLastError() ret=7a143d88
0033:Ret  KERNEL32.GetLastError() retval=00000002 ret=7a143d88 
--- snip ---

Unfortunately after pretending that the junction was created, there is a check
if the redirection succeeds by retrieving file attributes for each assembly -
so there has to be a real link...

The main problem is actually the conversion of supplied handle to something
meaningful for symlink(2).
There is no reliable way to get that path name back from the file descriptor.
Wine doesn't store this information (object name) anywhere.

So it boils down to unix style file descriptor (and associated inode) vs. 
systems calls that expect path names.
Actually it would be easier if there is *nix symlink() which accepts fd's or
inodes as parameter type :-(
Maybe the name/path information can be stored in wine server on object creation
to be later retrieved by various NtQueryXXX.

Regards

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

Dan Kegel  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]
         Depends on|                            |12401

--- Comment #16 from Dan Kegel   2008-04-07 07:19:45 ---
Created bug 12401 for junction points.

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

Rob Shearman  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|ole                         |kernel32

--- Comment #17 from Rob Shearman   2008-06-03 17:33:52 ---
Changing component to kernel32 from ole.

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #18 from Austin English   2008-06-20 15:05:19 ---
*** Bug 13997 has been marked as a duplicate of this bug. ***

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

James Hawkins  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #18 from Austin English   2008-06-20 15:05:19 ---
*** Bug 13997 has been marked as a duplicate of this bug. ***

--- Comment #19 from James Hawkins   2008-06-28 19:50:47 ---
*** Bug 14163 has been marked as a duplicate of this bug. ***

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

James Hawkins  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #20 from James Hawkins   2008-07-08 12:04:02 ---
*** Bug 14355 has been marked as a duplicate of this bug. ***

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

Austin English  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |10019

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

Dan Kegel  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |5054

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

Teemu Ikonen  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|                            |12852

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

Dan Kegel  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |12852
         Depends on|12852                       |

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

Jordan Bradley  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #21 from Jordan Bradley   2009-03-31 12:26:44 ---
So is there a fix? I changed the mode from XP to 2K and I still get the page
fault error.

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #22 from Anastasius Focht   2009-03-31 14:13:31 ---
Hello,

--- quote ---
So is there a fix? I changed the mode from XP to 2K and I still get the page
fault error.
--- quote ---

Please don't mix up different problems.
You're running into bug 10467

Please do yourself a favour and search appdb besides bugzilla before filing
bugs!
All problems are documented!

'winetricks' is the recommended way to install .NET Framework 2.0
Other install methods are not supported unless you know what you're doing.

Regards

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #23 from Anastasius Focht   2009-04-07 16:01:28 ---
Hello,

this specific problem is worked around by commit
8044c11ecfca09e2b643feccb95a4d8f645ba656 by not defaulting to NTFS anymore, see
comment #15 for analysis.

You might close this one but if the ongoing discussion results in current
default FS type to be changed/reverted again you have to *reopen* this bug.

The implementation of NTFS junction point API is tracked separately by bug
12401

Though I still recommend to use winetricks because most people tend to forget
to copy the unicode casing tables *before* running the .NET 2.0 installer (bug
10467).
I updated the appdb entry accordingly.

Regards

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

sl@shback  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #24 from sl@shback   2009-10-04 15:56:07 ---
*** Bug 20262 has been marked as a duplicate of this bug. ***

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #25 from sl@shback   2009-10-04 16:10:36 ---
(In reply to comment #23)
> Hello,
>
> this specific problem is worked around by commit
> 8044c11ecfca09e2b643feccb95a4d8f645ba656 by not defaulting to NTFS anymore, see
> comment #15 for analysis.

Thanks for telling, but which steps exactly are recommended to solve the bug
discribed?

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #26 from sl@shback   2009-10-04 16:39:28 ---
(In reply to comment #25)
> (In reply to comment #23)
> > Hello,
> >
> > this specific problem is worked around by commit
> > 8044c11ecfca09e2b643feccb95a4d8f645ba656 by not defaulting to NTFS anymore, see
> > comment #15 for analysis.
>
> Thanks for telling, but which steps exactly are recommended to solve the bug
> discribed?

Tests reveal: Windows mode = Win 2000 = RegScvcs.exe crashing
Windows mode = Win XP = Installer breaks "unexpectedly".

WHAT IS THE FIX FOR THIS?

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

Ken Sharp  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |dotnet, download, Installer

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #27 from sl@shback   2009-10-06 02:44:41 ---

Just to add this to all who think: "Wy isn´t this guys using winetricks?
I DID. When using winetricks, winversion will be switched to win 2000,
resulting in Regsvcs.exe crashing. Installing manually with winversion XP works
partially - Regsvcs.exe does not crash anymore, but results in THIS bug:
Installer crashes and tells the installation would have completed
"sucessfully". Don´t agree with that.

As it appears, WINE 1.1.30 cannot handle .NET 2.0 on a x86_64 system. Please
prove me different or provide EXACT steps to prevent the error happning.
Already submitted a complete compressed winedebug log to user "arethusa" on
IRC.

The steps mentioned on your glorious wiki simply DO NOT WORK.

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #28 from Dmitry Timoshkov   2009-10-06 04:12:07 ---
> The steps mentioned on your glorious wiki simply DO NOT WORK.

This is a bugzill, not a support forum. If the steps listed in the wiki
don't work for you, fell free to edit it with the working solution.

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #29 from sl@shback   2009-10-06 04:36:42 ---
(In reply to comment #28)
> > The steps mentioned on your glorious wiki simply DO NOT WORK.
>
> This is a bugzill, not a support forum. If the steps listed in the wiki
> don't work for you, fell free to edit it with the working solution.

Your answer is absolutely not acceptable for me.
Antasius Focht states: "...this specific problem is worked around by commit
8044c11ecfca09e2b643feccb95a4d8f645ba656 by not defaulting to NTFS anymore, see
comment #15 for analysis." Great - and what are the APPROPRIATE steps to work
around the installer crashing?

If you look at my previous comments you *might* realize that I am asking for
something. How would YOU provide the solution if you asked for it yourself?

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #30 from Vitaliy Margolen   2009-10-06 08:15:26 ---
(In reply to comment #29)
> How would YOU provide the solution if you asked for it yourself?

This is bugzilla, not support forum. This place does not provide solutions. It
collects unresolved problems. This bug is still open which means it's not
fixed. Is that so hard to understand?

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #31 from sl@shback   2009-10-06 12:35:30 ---
YES.

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #32 from Anastasius Focht   2009-10-06 14:42:43 ---
Hello,

--- quote ---
Antasius Focht states: "...this specific problem is worked around by commit
8044c11ecfca09e2b643feccb95a4d8f645ba656 by not defaulting to NTFS anymore, see
comment #15 for analysis." Great - and what are the APPROPRIATE steps to work
around the installer crashing?
--- quote ---

That comment was referring to an earlier state of the bug.
Commit 8044c11ecfca09e2b643feccb95a4d8f645ba656 was reverted because it caused
other apps to fail (defaulting to fat32 would have been the better choice as
some Windows apps can't cope with unixfs).

Anyway, if winetricks .NET 2.0 install worked for you before (<1.1.30), please
do regression test to identify the commit that broke it.

http://wiki.winehq.org/RegressionTesting

If you don't want to go though that process you could produce a debug log for
regsvcs.exe bootstrapping process (which is probably the one crashing here).

1. run winetricks dotnet20 on clean WINEPREFIX, dismiss the crash handler and
installer dialog (if any), wait a bit.
2. open console, kill any lingering wine processes if present (wineserver -k)
3. make sure Wine version is (still) set to "Windows 2000" (winecfg)
4. run the following in console (and dismiss crash handler again):

WINEDEBUG=+tid,+seh,+relay wine
"C:\windows\Microsoft.NET\Framework\v2.0.50727\RegSvcs.exe" /bootstrapi &>
log.txt

compress the resulting log with 'bzip2 -9 log.txt' and attach the file
'log.txt.bz2'.

Though you're probably better off with regression testing because bugs emerging
from managed executables are hard to diagnose  looking only at logs if
developers can't reproduce/debug it (code is jitted at this point).

Regards

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #33 from sl@shback   2009-10-09 13:14:19 ---
I just wish this freakin .NET 2 would work with WINE in its actual version.
Look, I´ve tested to install .NET 2 in WINE 1.1.16 - and it WORKED! Then I
upgraded to WINE 1.1.30 - and installed .NET 3.0: It never finishes. YOu might
say: "Boy, you cannot use a wineprefix of a different version". It was just
another cry out into the night.

But hey, I attached the suggested log. Take a look! ;)

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #34 from sl@shback   2009-10-09 13:17:02 ---
Created an attachment (id=23996)
 --> (http://bugs.winehq.org/attachment.cgi?id=23996)
Regsvcs bootstrap as suggested in comment #32

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

sl@shback  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #23996|Regsvcs bootstrap as        |Regsvcs.exe bootstrap as
        description|suggested in comment #32    |suggested in comment #32

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #35 from Dan Kegel   2009-10-09 13:22:04 ---
As Anastasius said, it is very helpful for us to know which
version (and which patch) broke your app.
Thank you for the information that .net 2.0 install
worked as you wanted in 1.1.16 but not in 1.1.30.
Now, can you narrow that down to the version that
caused the breakage?

And then the patch within the version, following
http://wiki.winehq.org/RegressionTesting ?
That's the kind of info that makes for great bug reports.
(You might even be able to script the regression search so you
don't have to run it repeatedly yourself.)

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #36 from sl@shback   2009-10-09 13:44:39 ---
Are you trying to say that the above posted log does not help any? How would
you script regression testing?

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #37 from Dan Kegel   2009-10-09 15:15:47 ---
I don't know if the log is helpful, it may well be.

Knowing which patch broke something is a pretty powerful signal, though,
and kind of trumps logs if it's available.

http://www.kernel.org/pub/software/scm/git/docs/git-bisect.html
says:
-- snip --
If you have a script that can tell if the current source code is good or bad,
you can bisect by issuing the command:

$ git bisect run my_script arguments
Note that the script (my_script in the above example) should exit with code 0
if the current source code is good, and exit with a code between 1 and 127
(inclusive), except 125, if the current source code is bad.
-- snip --

So potentially a script like
  rm -rf ~/.wine
  exec sh winetricks -q nocrashdialog dotnet20
would work as an argument to git bisect run.
I haven't verified whether the exit status is set properly, though.
One always has to tread carefully when using tools
like this, of course.

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #38 from Anastasius Focht   2009-10-10 03:55:34 ---
Hello,

looks like the default NT unicode case mapping table in your WINEPREFIX got
somehow corrupted.

Can you check if 'l_intl.nls' contained in your winetrickscache 'dotnet20'
folder is around 5K size?
If not, remove that file to force winetricks to redownload it (upon 'winetricks
dotnet20').
Repeat install steps (e.g. clean WINEPREFIX, winetricks dotnet20).

If that still doesn't work, check output of this:

wget http://kegel.com/wine/l_intl.nls -O
~/.wine/drive_c/windows/system32/l_intl.nls

Report back.

Regards

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #39 from sl@shback   2009-10-10 10:41:52 ---
Thanks Anastasius Focht. How did you find out about the corrupted NT unicode
case mapping table? It´s stunning, because noone seems to second the problem.

Your check revealed that either versions of l_intl.nls are the same size: 1018
B.

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #40 from Dan Kegel   2009-10-10 10:58:26 ---
AF is a giant among wine hackers... he's very good at diagnosing problems.

Did that solve your problem?

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #41 from sl@shback   2009-10-10 11:22:58 ---
Thanks for reporting back, Dan. His suggestion just included that I should
check the size of l_intl.nls. As it turns out, it is 1018 B in size. I then
executed his suggested command and it completed without any visual output on
console. Upon executing 'winetricks dotnet20' Regsvcs.exe crashed again.

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #42 from Dan Kegel   2009-10-10 11:31:31 ---
That file should be 5574 bytes long.

If wget on that file doesn't show this:

$ wget http://kegel.com/wine/l_intl.nls
--2009-10-10 09:30:26--  http://kegel.com/wine/l_intl.nls
Resolving kegel.com... 216.92.86.126
Connecting to kegel.com|216.92.86.126|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5574 (5.4K) [text/plain]
Saving to: `l_intl.nls'

100%[======================================>] 5,574       --.-K/s   in 0.1s

2009-10-10 09:30:26 (51.8 KB/s) - `l_intl.nls' saved [5574/5574]

something funny is going on.

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #43 from Anastasius Focht   2009-10-10 11:38:06 ---
Hello,

--- quote ---
As it turns out, it is 1018 B in size. I then
executed his suggested command and it completed without any visual output on
console. Upon executing 'winetricks dotnet20' Regsvcs.exe crashed again.
--- quote ---

1K is way too short. Did you really remove the file from _winetrickscache_?
Winetricks doesn't checksum that file hence corrupted one might get copied
again into WINEPREFIX.
Again: make sure 'l_intl.nls' is valid.
If it still crashes even with a valid 'l_intl.nls' (around 5K size), attach log
again (same procedure from comment #32).

Regards

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #44 from sl@shback   2009-10-10 11:56:13 ---
Interesting results. Manually executing 'wget http://kegel.com/wine/l_intl.nls'
results in a file with 5574 bytes (which should be correct). I then replaced
l_intl.nls both in winetrickscache (there the file was broken) and in
~/.wine/drive_c/windows/system32/ with the new one and now Regsvcs.exe doesn´t
crash, but rather setup took its time. 3..2..1: AND THAT DID THE JOB! ;)

Thank you Mr. Focht and Mr. Kegel for your great support - even if this is not
a forum to solve such problems. I´d love to see a corresponding warning in the
HOWTO to check l_intl.nls for its correct size.

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #45 from Austin English   2009-10-10 14:26:08 ---
(In reply to comment #44)
> Interesting results. Manually executing 'wget http://kegel.com/wine/l_intl.nls'
> results in a file with 5574 bytes (which should be correct). I then replaced
> l_intl.nls both in winetrickscache (there the file was broken) and in
> ~/.wine/drive_c/windows/system32/ with the new one and now Regsvcs.exe doesn´t
> crash, but rather setup took its time. 3..2..1: AND THAT DID THE JOB! ;)
>
> Thank you Mr. Focht and Mr. Kegel for your great support - even if this is not
> a forum to solve such problems. I´d love to see a corresponding warning in the
> HOWTO to check l_intl.nls for its correct size.

No need, I've updated winetricks to be sure to sha1sum l_intl.nls.

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

Nikolay Sivov  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|10019                       |
                 CC|                            |[e-mail]

--- Comment #46 from Nikolay Sivov   2009-12-29 15:26:34 ---
*** Bug 10019 has been marked as a duplicate of this bug. ***

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

Luke Bratch  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

Ian Dall  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #47 from Ian Dall   2010-04-11 19:19:50 ---
I am confused by comment #44. I still get RegSvcs.exe page faults with a valid
l_intl.nls.

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

Xavier Vachon  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #48 from Xavier Vachon   2010-06-30 08:14:48 ---
Still a bug with wine 1.2-rc5

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #49 from Austin English   2010-08-26 11:27:38 ---
Still in wine-1.3.1-182-g56b8d5d.

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

wineatic  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 10601] .NET Framework 2.0: Installation Fails in winxp mode

http://bugs.winehq.org/show_bug.cgi?id=10601

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #50 from Anastasius Focht  2011-06-19 12:26:34 CDT ---
*** Bug 27538 has been marked as a duplicate of this bug. ***

[Bug 10601] Microsoft .NET Framework: GAC API for managed assembly installation needs reparse point/junction API support (.NET Framework 2.0 installer in XP mode and other apps that make use of GAC API)

http://bugs.winehq.org/show_bug.cgi?id=10601

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|.NET Framework 2.0:         |Microsoft .NET Framework:
                   |Installation Fails in winxp |GAC API for managed
                   |mode                        |assembly installation needs
                   |                            |reparse point/junction API
                   |                            |support (.NET Framework 2.0
                   |                            |installer in XP mode and
                   |                            |other apps that make use of
                   |                            |GAC API)

--- Comment #51 from Anastasius Focht  2011-06-19 12:34:10 CDT ---
Hello,

refining summary...
Obviously still present.

$ wine --version
wine-1.3.22-203-gac90c1b

Regards

[Bug 10601] Microsoft .NET Framework: GAC API for managed assembly installation needs reparse point/junction API support (.NET Framework 2.0 installer in XP mode and other apps that make use of GAC API)

http://bugs.winehq.org/show_bug.cgi?id=10601

Jordan Bradley  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|[e-mail]  |

[Bug 10601] Microsoft .NET Framework: GAC API for managed assembly installation needs reparse point/junction API support (.NET Framework 2.0, 3.0, 4.0 installers and other apps that make use of GAC API)

http://bugs.winehq.org/show_bug.cgi?id=10601

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Microsoft .NET Framework:   |Microsoft .NET Framework:
                   |GAC API for managed         |GAC API for managed
                   |assembly installation needs |assembly installation needs
                   |reparse point/junction API  |reparse point/junction API
                   |support (.NET Framework 2.0 |support (.NET Framework
                   |installer in XP mode and    |2.0, 3.0, 4.0 installers
                   |other apps that make use of |and other apps that make
                   |GAC API)                    |use of GAC API)

--- Comment #52 from Anastasius Focht  2012-02-12 11:16:04 CST ---
Hello,

refining summary...
Obviously still present.

$ wine --version
wine-1.4-rc3

Regards

[Bug 10601] Microsoft .NET Framework: GAC API for managed assembly installation needs reparse point/junction API support (.NET Framework 2.0, 3.0, 4.0 installers and other apps that make use of GAC API)

http://bugs.winehq.org/show_bug.cgi?id=10601

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |29905

[Bug 10601] Microsoft .NET Framework: GAC API for managed assembly installation needs reparse point/junction API support (.NET Framework 2.0, 3.0, 4.0 installers and other apps that make use of GAC API)

http://bugs.winehq.org/show_bug.cgi?id=10601

Sylvain Petreolle  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 10601] Microsoft .NET Framework: GAC API for managed assembly installation needs reparse point/junction API support (.NET Framework 2.0, 3.0, 4.0 installers and other apps that make use of GAC API)

http://bugs.winehq.org/show_bug.cgi?id=10601

Rosanne DiMesio  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #53 from Rosanne DiMesio  2012-07-23 12:16:18 CDT ---
*** Bug 31294 has been marked as a duplicate of this bug. ***

[Bug 10601] Microsoft .NET Framework: GAC API for managed assembly installation needs reparse point/junction API support (.NET Framework 2.0, 3.0, 4.0 installers and other apps that make use of GAC API)

http://bugs.winehq.org/show_bug.cgi?id=10601

--- Comment #54 from Szymon  2012-07-23 20:53:24 CDT ---
Problem with .NET 4.0 reproduced with newest wine version I can download:
1. I uninstalled wine and connected packages by Synaptic ("completly remove")
2. rf -rf .wine/
3. install some packages required according to some descriptions (leak of
official documentation for building wine from source):
flex
bison
libx11-dev (with plenty of dependencies)
freetype2-demod
libfreetype6-dev
fronforge
x11proto-xf86dga-dev
4. execute install-wine-deps.sh (from
http://winezeug.googlecode.com/svn/trunk/install-wine-deps.sh)
5. configure ; make depend ; make ; sudo make install in wine-1.5.9 source dir
6. /usr/local/bin/winecfg (twice)
   (there I've got some 
    err:xrandr:xrandr12_init_modes Failed to get output info.
    )
7. ./winetricks dotnet40
   .... (many output on terminal, see bellow) ...
   and popup said 
   "Program .NET Framework 4 nie został zainstalowany ponieważ:
    HRESULT 0x80070643"
   (Program .NET Framework 4 hasn't been installed because: 
    HRESULT 0x80070643)

================ terminal output (how add attachemnt to comment?)===========
sfp@sfp-laptop:/home/sfp/src$ wine --version
wine-1.5.9
sfp@sfp-laptop:/home/sfp/src$ ./winetricks dotnet40
Executing w_do_call dotnet40
Executing load_dotnet40
------------------------------------------------------
dotnet40 does not yet fully work or install on wine.  Caveat emptor.
------------------------------------------------------
Executing mkdir -p /home/sfp//.cache/winetricks/dotnet40
DELETE - HKLM\Software\Microsoft\NET Framework Setup\NDP\v4 (null) 0 0 1
err:xrandr:xrandr12_init_modes Failed to get output info.
Operacja zakończona pomyślnie
------------------------------------------------------
The installer will fail after the first try, don't freak out.
------------------------------------------------------
Executing rm /home/sfp//.wine/dosdevices/c:/windows/system32/mscoree.dll
err:xrandr:xrandr12_init_modes Failed to get output info.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessDEPPolicy (3): stub
fixme:clusapi:OpenCluster ((null)) stub!
fixme:clusapi:ClusterOpenEnum (0xdeadbeef, 4) stub!
fixme:clusapi:ClusterEnum (0xdeadbeef, 0, 0x32f860, 0x134e70, 261) stub!
fixme:clusapi:ClusterCloseEnum (0xdeadbeef) stub!
fixme:clusapi:CloseCluster (0xdeadbeef) stub!
fixme:advapi:DecryptFileW L"C:\9e71e60c005b1547b94eadf42f12d7\" 00000000
err:xrandr:xrandr12_init_modes Failed to get output info.
err:xrandr:xrandr12_init_modes Failed to get output info.
fixme:advapi:RegisterTraceGuidsW (0x6cd15f38, 0x6cd20180,
{e2821408-c59d-418f-ad3f-aa4e792aeb79}, 1, 0x33fc90, (null), (null),
0x6cd20188,): stub
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessDEPPolicy (1): stub
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:thread:SetThreadStackGuarantee (0x33fb68): stub
fixme:advapi:LsaOpenPolicy ((null),0x33f474,0x00000001,0x33f49c) stub
fixme:advapi:LsaClose (0xcafe) stub
fixme:msxml:domdoc_putref_schemas (0x1dda60)->({VT_DISPATCH: 0x7e8a38}):
semi-stub
fixme:msxml:domdoc_get_readyState stub! (0x1dda60)->(0x33f3a0)
fixme:propsheet:PROPSHEET_SetHeaderTitleW (0x5005c, 0, L"Instalator programu
.NET Framework 4"): stub
fixme:propsheet:PROPSHEET_SetHeaderSubTitleW (0x5005c, 0, L"Zaakceptuj
postanowienia licencyjne, aby kontynuowa\0107."): stub
fixme:propsheet:PROPSHEET_SetHeaderTitleW (0x5005c, 2, L"Post\0119p
instalacji"): stub
fixme:propsheet:PROPSHEET_SetHeaderSubTitleW (0x5005c, 2, L"Program .NET
Framework jest instalowany, czekaj."): stub
fixme:storage:create_storagefile Storage share mode not implemented.
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
err:rpc:I_RpcGetBuffer no binding
err:rpc:I_RpcGetBuffer no binding
fixme:loadperf:UnloadPerfCounterTextStringsW
(L"C:\windows\system32\unlodctr.exe /m:""", 0): stub
fixme:loadperf:UnloadPerfCounterTextStringsW
(L"C:\windows\system32\unlodctr.exe "ServiceModelEndpoint 4.0.0.0"", 0):
stub
fixme:loadperf:UnloadPerfCounterTextStringsW
(L"C:\windows\system32\unlodctr.exe "ServiceModelOperation 4.0.0.0"", 0):
stub
fixme:loadperf:UnloadPerfCounterTextStringsW
(L"C:\windows\system32\unlodctr.exe "ServiceModelService 4.0.0.0"", 0):
stub
fixme:loadperf:UnloadPerfCounterTextStringsW
(L"C:\windows\system32\unlodctr.exe "SMSvcHost 4.0.0.0"", 0): stub
fixme:loadperf:UnloadPerfCounterTextStringsW
(L"C:\windows\system32\unlodctr.exe "MSDTC Bridge 4.0.0.0"", 0): stub
fixme:imagehlp:BindImageEx (0,
"C:\windows\Microsoft.NET\Framework\v4.0.30319\clr.dll",
"C:\windows\Microsoft.NET\Framework\v4.0.30319\", (null), (nil)): stub
fixme:imagehlp:BindImageEx (0,
"C:\windows\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll",
"C:\windows\Microsoft.NET\Framework\v4.0.30319\", (null), (nil)): stub
fixme:imagehlp:BindImageEx (0, "C:\windows\system32\mscoree.dll",
"C:\windows\system32\", (null), (nil)): stub
fixme:imagehlp:BindImageEx (0,
"C:\windows\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll",
"C:\windows\Microsoft.NET\Framework\v4.0.30319\", (null), (nil)): stub
fixme:imagehlp:BindImageEx (0, "C:\windows\system32\msvcr100_clr0400.dll",
"C:\windows\system32\", (null), (nil)): stub
fixme:imagehlp:BindImageEx (0,
"C:\windows\Microsoft.NET\Framework\v4.0.30319\clrjit.dll", "", (null),
(nil)): stub
fixme:imagehlp:BindImageEx (0,
"C:\windows\Microsoft.NET\Framework\v4.0.30319\mscorpe.dll",
"C:\windows\Microsoft.NET\Framework\v4.0.30319\", (null), (nil)): stub
fixme:imagehlp:BindImageEx (0,
"C:\windows\Microsoft.NET\Framework\v4.0.30319\mscorpehost.dll",
"C:\windows\Microsoft.NET\Framework\v4.0.30319\", (null), (nil)): stub
fixme:imagehlp:BindImageEx (0,
"C:\windows\Microsoft.NET\Framework\v4.0.30319\vbc.exe",
"C:\windows\Microsoft.NET\Framework\v4.0.30319\", (null), (nil)): stub
fixme:loadperf:LoadPerfCounterTextStringsW (L"C:\windows\system32\lodctr.exe
"C:\windows\Microsoft.NET\Framework\v4.0.30319\_ServiceModelEndpointPerfCounters.ini"",
0): stub
fixme:loadperf:LoadPerfCounterTextStringsW (L"C:\windows\system32\lodctr.exe
"C:\windows\Microsoft.NET\Framework\v4.0.30319\_ServiceModelOperationPerfCounters.ini"",
0): stub
fixme:loadperf:LoadPerfCounterTextStringsW (L"C:\windows\system32\lodctr.exe
"C:\windows\Microsoft.NET\Framework\v4.0.30319\_ServiceModelServicePerfCounters.ini"",
0): stub
fixme:loadperf:LoadPerfCounterTextStringsW (L"C:\windows\system32\lodctr.exe
"C:\windows\Microsoft.NET\Framework\v4.0.30319\_SMSvcHostPerfCounters.ini"",
0): stub
fixme:loadperf:LoadPerfCounterTextStringsW (L"C:\windows\system32\lodctr.exe
"C:\windows\Microsoft.NET\Framework\v4.0.30319\_TransactionBridgePerfCounters.ini"",
0): stub
err:xrandr:xrandr12_init_modes Failed to get output info.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessDEPPolicy (1): stub
err:xrandr:xrandr12_init_modes Failed to get output info.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessDEPPolicy (1): stub
err:xrandr:xrandr12_init_modes Failed to get output info.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessDEPPolicy (1): stub
err:xrandr:xrandr12_init_modes Failed to get output info.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessDEPPolicy (1): stub
err:xrandr:xrandr12_init_modes Failed to get output info.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessDEPPolicy (1): stub
err:xrandr:xrandr12_init_modes Failed to get output info.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessDEPPolicy (1): stub
err:xrandr:xrandr12_init_modes Failed to get output info.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessDEPPolicy (1): stub
fixme:mofcomp:wmain stub
fixme:mofcomp:wmain stub
err:rpc:I_RpcGetBuffer no binding
err:rpc:I_RpcGetBuffer no binding
err:rpc:I_RpcGetBuffer no binding
err:rpc:I_RpcGetBuffer no binding
err:rpc:I_RpcGetBuffer no binding
err:rpc:I_RpcGetBuffer no binding
err:rpc:I_RpcGetBuffer no binding
err:rpc:I_RpcGetBuffer no binding
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
fixme:ntdll:server_ioctl_file Unsupported ioctl 900a4 (device=9 access=0
func=29 method=0)
fixme:ntdll:server_ioctl_file Unsupported ioctl 900a4 (device=9 access=0
func=29 method=0)
fixme:ntdll:server_ioctl_file Unsupported ioctl 900a4 (device=9 access=0
func=29 method=0)
err:msi:ITERATE_Actions Execution halted, action L"InstallFinalize" returned
1603
fixme:msi:ACTION_CustomAction msidbCustomActionTypeTSAware not handled
err:rpc:I_RpcGetBuffer no binding
    fixme:advapi:LsaOpenPolicy ((null),0x33f2c0,0x00000001,0x33f2e8) stub
fixme:advapi:LsaClose (0xcafe) stub
Using native override for following DLLs: mscoree
Executing winetricks_early_wine regedit
C:\windows\Temp_dotnet40\override-dll.reg
ADD - HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Full Install 0
REG_DWORD 0001 1
err:xrandr:xrandr12_init_modes Failed to get output info.
Operacja zakończona pomyślnie
ADD - HKLM\Software\Microsoft\NET Framework Setup\NDP\v4\Full Version 0 REG_SZ
4.0.30319 1
err:xrandr:xrandr12_init_modes Failed to get output info.
Operacja zakończona pomyślnie
tar: Rozmiar rekordu = 8 bloków
gacutil.exe
gacutil.exe.config
err:xrandr:xrandr12_init_modes Failed to get output info.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessDEPPolicy (1): stub
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
Microsoft (R) .NET Global Assembly Cache Utility.  Version 4.0.30319.1
Copyright (c) Microsoft Corporation.  All rights reserved.

err:xrandr:xrandr12_init_modes Failed to get output info.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessDEPPolicy (1): stub
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
Microsoft (R) .NET Global Assembly Cache Utility.  Version 4.0.30319.1
Copyright (c) Microsoft Corporation.  All rights reserved.

fixme:module:GetModuleHandleExW should pin refcount for 0x79000000
err:xrandr:xrandr12_init_modes Failed to get output info.
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
fixme:process:SetProcessDEPPolicy (1): stub
fixme:heap:HeapSetInformation (nil) 1 (nil) 0
Microsoft (R) .NET Global Assembly Cache Utility.  Version 4.0.30319.1
Copyright (c) Microsoft Corporation.  All rights reserved.

(last two verses repeated, without order, unless stopped by Ctrl-C)

[Bug 10601] Microsoft .NET Framework: GAC API for managed assembly installation needs reparse point/junction API support (.NET Framework 2.0, 3.0, 4.0 installers and other apps that make use of GAC API)

http://bugs.winehq.org/show_bug.cgi?id=10601

Qian Hong  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 10601] Microsoft .NET Framework: GAC API for managed assembly installation needs reparse point/junction API support (.NET Framework 2.0, 3.0, 4.0 installers and other apps that make use of GAC API)

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

David Hughes  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

[Bug 10601] Microsoft .NET Framework: GAC API for managed assembly installation needs reparse point/junction API support (.NET Framework 2.0, 3.0, 4.0 installers and other apps that make use of GAC API)

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

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
          Component|kernel32                    |ntdll
         Resolution|---                         |DUPLICATE

--- Comment #55 from Anastasius Focht  ---
Hello folks,

I'm merging this one into bug 12401

It's unfortunate that Dan decided to create another one, effectively
duplicating the issue.
Both collected now a number of dupes on their own.

Regards

*** This bug has been marked as a duplicate of bug 12401 ***

[Bug 10601] Microsoft .NET Framework: GAC API for managed assembly installation needs reparse point/junction API support (.NET Framework 2.0, 3.0, 4.0 installers and other apps that make use of GAC API)

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

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|12401                       |

[Bug 10601] Microsoft .NET Framework: GAC API for managed assembly installation needs reparse point/junction API support (.NET Framework 2.0, 3.0, 4.0 installers and other apps that make use of GAC API)

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

Ken Sharp  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |CLOSED

--- Comment #56 from Ken Sharp  ---
Closing

[Bug 10601] Microsoft .NET Framework: GAC API for managed assembly installation needs reparse point/junction API support (.NET Framework 2.0, 3.0, 4.0 installers and other apps that make use of GAC API)

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

Sylvain Petreolle  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|[e-mail]         |

[Bug 10601] Microsoft .NET Framework: GAC API for managed assembly installation needs reparse point/junction API support (.NET Framework 2.0, 3.0, 4.0 installers and other apps that make use of GAC API)

[WineHQ Bugzilla]

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

Anastasius Focht  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                URL|http://www.microsoft.com/do |https://web.archive.org/web
                   |wnloads/details.aspx?family |/20071013090007/http://down
                   |id=0856eacb-4362-4b0d-8edd- |load.microsoft.com/download
                   |aab15c5e04f5&displaylang=en |/5/6/7/567758a3-759e-473e-b
                   |                            |f8f-52154438565a/dotnetfx.e
                   |                            |xe

--- Comment #57 from Anastasius Focht  ---
Hello folks,

adding stable download link via Internet Archive for documentation.

https://web.archive.org/web/20071013090007/http://download.microsoft.com/dow...

https://www.virustotal.com/gui/file/46693d9b74d12454d117cc61ff2e9481cabb100b...

$ sha1sum dotnetfx.exe 
a3625c59d7a2995fb60877b5f5324892a1693b2a  dotnetfx.exe

$ du -sh dotnetfx.exe 
23M    dotnetfx.exe

Regards