I have the same question 3. Report abuse. Details required :. Cancel Submit. Mouneshwar R. Hi aliafshar, Could you please provide the error message and error code that you receive when you try to install Microsoft. Mouneshwar R — Microsoft Support Visit our Microsoft Answers Feedback Forum and let us know what you think. How satisfied are you with this reply? I'm attaching the Error log here.
I'm using Windows Server SP2 and have already installed. Net Framework 2. Guide me please to solve the problem. Jeff Beckham. Join our community to see this answer! Unlock 1 Answer and 2 Comments. Andrew Hancock - VMware vExpert. See if this solution works for you by signing up for a 7 day free trial.
What do I get with a subscription? With your subscription - you'll gain access to our exclusive IT community of thousands of IT pros. I did some testing with a today: I'm getting different errors now with the same DLL setup. It appears that ngen. I think vcrun installs now though? I'm working on logging the dotnet35sp1 installer with log2 but am running into some strangeness.
I'll try to finish that logging and upload some analysis tomorrow or so. I'm not sure which exact commit fixed it, but as of Box86 a19e3ed , dotnet35sp1 seems to completely install on its own!
This has been such a tricky installer that I want to do a little more testing before we finally close the issue and add it to the compatability list. But I'm pretty stoked that it's installing! Nice work. Been kinda busy lately but got a chance to experiment with dotnet35 some more with the new box86 updates. It seems to be crashing again. Jan 1 db5efa8 installs completely. Jan 2 eca39e6 the installer fails.
This took forever to find, but it's the eca39e6 commit that appears to have broken the dotnet35sp1 installer dotnet35sp1 installer installs completely with dc8. I found something interesting after testing some winlink stuff: The error dialog box in dotnet35sp1 installer seems to go away if I install crypt32 before running the installer. But the installer then says it can't install properly, just doesn't ask to send an error report. If I install dotnet35sp1 with crypt32, then I don't get the error dialog box in the dotnet35sp1 installer, but the installer fails here.
I tried secur32, setupapi, and ole32 too separately and in some combos , but they seem to crash the installer. I think I tracked that error dialogue in the dotnet35sp1 installer to this commit: dc07d47 - error dialogue, but dotnet installs successfully db5efa8 - installs without any errors.
Just an update that the new libcrypt wrapper in 0ffc seems to cause dotnet35sp1 installer to crash again fairly early in the install process though, which makes testing faster.
It would be great to have crypt32 and libcrypt wrapped though for compatability of dotnet programs. I'm gonna test this wrapper on Winlink next with a side-loaded dotnet35sp1 install to see how it helps Winlink. I tried dropping in a native crypt Another regression just for a new library wrapping? This is so strange. Also, this library have 6 functions wrapped! I'm trying to stabilise things but I seems to make things worse and worse for the last 2 weeks.
I think you are making it more stable in a general trend being more and more compatability - it's that there are so many moving pieces that it's like a cha-cha two steps forward, one step back haha.
The regression I found yesterday was from Jan still I just didn't find it till now , and having this libcrypt is really nice since it will help other dotnet applications. I also noticed that in older builds that install dotnet35sp1, if I use a native crypt So I think this is on the right track.
Not sure if this helps, but I logged box86 db5efa8 which installs dotnet35sp1 installer log here , then I logged box86 e which still has a crash in dotnet35sp1 installer log here. Later on in the log of the crashing box86 build, we see a couple err:mscoree:LoadLibraryShim error reading registry key for installroot 's pop up too. It's possible that these registry key errors are due to ngen not having been run. After installing dotnet35sp1 with db5efa8 , then installing box86 9c5a9eb latest nightly build in test.
Incredible work, Seb. This still seems to be installing nicely with v0. Dynarec speeds up the installer considerably so that install takes about 25 minutes on a Pi4. I'll update the compatibility list. Skip to content. Star 1. New issue. Jump to bottom. NET 3. Copy link. Overview I'd like to get dotnet35sp1 to install so that Winlink will run more stably RMS Express opens with mono, but doesn't function correctly since it doesn't allow us to open modems through the RMS Express program.
Segmentation fault. Contributor Author. Many you're fast. DllRegisterServer, aborting wine: Unimplemented function prntvpt. DllRegisterServer called at address 7B00F thread 01a4 , starting debugger DllRegisterServer called at address 7B00F thread 03c8 , starting debugger DllRegisterServer called at address 7B00F thread , starting debugger Box86 with Dynarec v0.
EDIT: Here's the program when olly loads its entrypoint I'm a newb reverser and don't know how to dump a log of ollydbg steps, but the wine terminal output looked like this on x86 Linux. EXE Box86 with Dynarec v0. DllRegisterServer, aborting. WheezyE mentioned this issue Oct 25, WinRPR DllRegisterServer, aborting return 0xB Interesting, this error is referencing a different memory address now with the newer Box86 verison I'm using.
NET Runtime version 2. Trying dotnet30 next All rights reserved. I'll probably get some time to test all this on Sunday-Wed. Next step in the install chain is dotnet45sp1.
I'll test this after work today! Occasionally a program will keep crashing unless I do this first wineserver -k wine wineboot wineserver -k. I did some more narrowing-down using git checkout just to make sure, and it's the libxml2 improved wrapping that seems to break XPSEPSC Dec 1 aac is the last commit that works for update.
Dec 2 1ba is the first commit that breaks the running of update. I might transfer this wineprefix to my x86 Linux computer and see if programs run on it Update: Transferring the wineprefix works! Takes about 20 minutes I think.
0コメント