Windows 10: Windows loader cannot find private dlls for symlink'd executables

-- DISCLAIMER: this is not a question but a bug report -- I cannot use the Feedback Hub because of policy restrictions in my organization


A process loading dynamic libraries follows a search strategy that typically includes the directory of the executable that initiated the process, effectively enabling private libraries to be used.


If the process has been initiated from a symbolic link to an executable (and that symlink is in a directory other than the target of the symlink), then the search of private dlls is broken, as the system is actually searching into the directory containing the symbolic link instead of the directory of the target executable.


My system is a Windows 10 Enterprise 1809 build 17763.134

:)

 

Symlink deleted with Windows 10 upgrade

Hi Aydee,

Thank you for posting your query in Microsoft Community.

Please provide the following information with us to understand the issue better.

• When you upgrade to Windows 10, you will be able to see the report of things needs to be taken care after upgrade, did you get any such report referring to Symlink?

I would like to inform you that this might have happened due to incompatibility of Symlink with Windows 10, try upgrading to the latest version of Symlink.

If that does not help, install the Symlink in compatibility mode and check if that helps



Install the software in compatibility mode.



a. Locate the executable file (.exe file) for the Symlink.

b. Right-click the file, and then click Properties.

c. In the Package Name Properties dialog box, click the Compatibility tab.

d. Click to select the Run this program in compatibility mode for check box, click Windows 8.1 with which it is compatible with in the Run this program in compatibility mode for list, and then click OK.

e. Double-click the executable file to start the Symlink.



For further assistance please get in touch with Symlink support, so that they can assist you better.

Hope these information helps, please get back to us for future support, we’ll be glad to assist you further.



Thank you.

 

How do I remove the Linux Boot Loader?

You don't actually uninstall a boot loader but replace it with another.

You cannot get Ubuntu to start on a Windows' boot loader, it needs to be GRUB (or an open source equivalent).

Any ways, to get the Windows' boot loader back up, you need to insert your WIN7 installer disk and select the repair option>startup repair. I am assuming the WIN7 will use a similar setup menu as VISTA.

Follow the guide here for step by step intructions: http://neosmart.net/wiki/display/EBCD/Recovering+the+Vista+Bootloader+from+the+DVD

After that, just format the partition/disk that ubuntu is on...

 

dll file not found after Creator's Update, Code Execution Cannot Proceed

Hi Aberfoyle,

It is possible that the
.dll file was corrupted during the update causing the error to occur.
To better assist you, kindly find the
.dll file
in
c:\Windows\System32. If you can find the
.dll file, it means that we need to
register
your
.dll file
to your
Operating System
for it to
work. To do this, we need to
unregister
the
.dll file
first and
re-register
it. Here are the steps on how to do so:

To unregister the .dll file:

• 
  Press
  Windows key + R, type
  Regsvr32 /u c:\Windows\System32\VCRUNTIME140.dll
  and hit
  Enter/OK.
  

To re-register the .dll file:

• 
  Press
  Windows key + R, type
  Regsvr32 c:\Windows\System32\VCRUNTIME140.dll
  and hit
  Enter/OK.
  

If you cannot find the
.dll
file in
c:\Windows\System32,
kindly run these methods of troubleshooting
so that we will know if the issue is within/not within the
Operating System:

Method 1:
Run SFC Scan.  

SFC
will
scan
and
run
an
automatic repair
to any
corrupted system files
that it will detect. We suggest that you perform it twice. To run an
SFC scan, follow these steps:  

• 
  Run
  Command Prompt as Administrator.  
  
• 
  Type
  sfc /scannow
  and hit
  Enter.   
  

Note:
Kindly run
SFC twice or thrice
and check for results before you proceed to the next method.

Method 2: Clean Boot.

Clean Boot
will
stop or disable
the
applications
that are running in your
computer's background.
To perform a
Clean Boot, click
here.

Note:
Reset the computer back to
Normal Mode
once you are done with the troubleshooting by following the section
"How to reset the computer to start normally after clean boot troubleshooting"
from the same article.

After performing these
methods of troubleshooting
and still the issue persists, we suggest that you contact your
computer/laptop manufacturer
for further assistance.

Update us on how it goes.

Regards.