-
Notifications
You must be signed in to change notification settings - Fork 513
'Unable to load DLL' exception on extension start #1633
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
That is rather strange. I assume you can start Windows PowerShell fine? Can you give the output of |
Yes, PowerShell is working fine otherwise. Here's
|
One more followup question: have you been successfully using the extension before and the new release caused this bug? |
If there are any other configurations, paths, or stack traces you can tell us about, or any other possibly relevant information, that would be very handy |
I'm going to look into this in the next week. @adityapatwardhan, @daxian-dbw, @SteveL-MSFT I might need your insight. |
I'm new to PowerShell, so I just installed the extension for the first time. I can't think of much more that would help... Do let me know if I can be of further assistance. |
I do have same problem with PowerShell Extension in VSCode. The problem starts this morning after reload of vscode to I found 'api-ms-win-core-sysinfo-l1-2-0.dll' on another machine. I added the file to 'C:\Program Files\Microsoft VS Code' with no succes even after restart vscode. I add 'api-ms-win-core-sysinfo-l1-2-0.dll' to 'C:\Windows\System32' with succes. Everything looks fine, but there is still an error in EditorServices.log My Diagnostic logfiles are attached. |
I am seeing the same issue, starting this morning with the new 1.10.0 update of Yesterday the 1.9.0 version was working without issue. I couldn't identify where the EDIT: Following this link, I was able to downgrade back to v1.9.0, and it is working again. Also, to prevent reinstalling v1.10.0, uncheck the following setting in vscode: |
Ok I'm looking into this. Hoping to get it fixed in the next week. We ship the DLL from this nuget package to log OSArchitecture among other things. We have to reassemble the DLLs in the module ourselves to make it cross platform. You'll see that here. If you manage locate the right DLL on your machine, it needs to go This should be possible to accomplish at build time for us as soon as I work out what the best way of going about this is. |
Looks like this is https://github.com/dotnet/corefx/issues/13566. I'm looking into where to get the appropriate DLL. |
Here's the required file for now, taken from the nuget package. You can unzip it and put it into (GitHub doesn't allow non-zip attachments) |
I will add this to our build as well. I anticipate a bugfix release in the next week or two. |
@gtaylor1981 Thanks for all the info you provided too. That stack trace was invaluable. |
I've spent quite a while looking through this and haven't been able to make much sense of it. I've opened up a new issue in corefx, as linked above. |
I had this issue as well but only on my Windows 7 SP1 desktop but not on MacOS. |
We've released a fix for this in PowerShell/PowerShellEditorServices#808. This is a Windows 7 specific problem that occurs because of a strange hole in a .NET API we depended on. We've worked around that issue now, but I also recommend upgrading your .NET version to at least 4.7.2 if possible (that's got all the cross-platform APIs built in). Please comment here if you still experience problems. |
I just updated to v1.10.1 and everything's working well. Thanks for the quick response! |
Glad to hear, @gtaylor1981! |
The response I've gotten from corefx is that we should upgrade to .NET Standard 2.0, which is .NET Framework 4.6.1 equivalent. We've already done this downstream in the 2.0.0 build, so I think we should invest there. |
Uh oh!
There was an error while loading. Please reload this page.
Issue Type: Bug
After installing PowerShell extension and opening a blank *.ps1 file, I immediately see the following exception in the Terminal window (PowerShell Integrated Console):
Unable to load DLL 'api-ms-win-core-sysinfo-l1-2-0.dll': The specified module could not be found.
Here's the (verbose) logs:
Following this, a popup informs me "The language service could not be started", with the output showing:
General Info
$PSVersionTable
VS Code Info
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
video_decode: enabled
video_encode: enabled
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: