I've not tested this out yet but have knocked up a quick batch file to install (put it next to Setup.exe along with the sqlunirl.dll grabbed from the temp folder from a previous install attempt): takeown /f C:\Windows\SysWOW64\sqlunirl.dll /a Just in case, I've also copied it to other folders that have executables in too. However the SQL Service Manager app then refuses to start, but since exes always look for dlls in their own folder first, put that same dll in C:\Program Files (x86)\Microsoft SQL Server\80\Tools\Binn. If I change the owner and permissions of that dll, I can then replace it with the extracted one, install MSDE, and afterwards replace it with the original Win10 one. No dependency loading issues found with any of them so I tried copying them all to C:\Windows\SysWow64, but one of them (sqlunirl.dll) got access denied as it is a part of the OS. I found that it was extracting several dlls to the temp folder during install and the MSI log was complaining about loading one of them.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |