Product and Version [VS/VSCode]: VSCode
OS Version [macOS/Windows]: Windows 10
Live Share Extension Version: 0.2.146
Target Platform or Language [e.g. Node.js]: Node.js
Steps to Reproduce / Scenario:
[Client I] Trace log: C:\Users\lkupke\AppData\Local\Temp\VSFeedbackVSRTCLogs\20180216_195153_VSCode.log
[Client I] Did not find user settings at C:\Users\lkupke\.vs-liveshare-settings.json
[Client I] Passed version check for Windows: found 10.0.14393
A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in 'C:\Users\lkupke\.vscode\extensions\ms-vsliveshare.vsliveshare-0.2.146\dotnet_modules\'.
[Client.Agent I] Agent terminated with exit code: 2147516547 and signal null
I am unable to get the Sign In button on the bottom screen. Is there some dependency that I need for my computer?
The extension on first run should be downloading the dotnet-runtime and copying it to this dotnet_modules folder. Can you check if hostpolicy.dll is present anywhere under C:\Users\lkupke\.vscode\extensions\ms-vsliveshare.vsliveshare-0.2.146\dotnet_modules\. It's supposed to get unzipped into a subfolder and then moved over.
@LmKupke Could you run the following command and then drag-and-drop the resulting files.txt file into a response to this issue? dir /s /b /a:d > files.txt. That will allow us to see what the contents of your Live Share extension looks like.
@srivatsn I checked the folder and didn't see any hostpolicy.dll in the folder and no zipped files as well.
@lostintangent what directory should I be executing this command from the ms-vsliveshare?
@LmKupke Oops, apologies for forgetting to ask that. Could you run that command from the C:\Users\lkupke\.vscode\extensions\ms-vsliveshare.vsliveshare-0.2.146\dotnet_modules\ folder?
@lostintangent I ran the command and got an empty files.txt file.
$ dir /s /b /a:d > files.txt
dir: cannot access '/s': No such file or directory
dir: cannot access '/b': No such file or directory
dir: cannot access '/a:d': No such file or directory
I executed the command from the /c/users/lkupke/.vscode/extensions/ms-vsliveshare.vsliveshare-0.2.146/dotnet_modules
@LmKupke Ah OK, are you using Windows Subsystem for Linux? The previous command was for use with cmd.exe, so that wouldn't work with Bash, which explains the error you saw. If so, could you run du | awk '{print $2}' > files.txt from the same directory?
@lostintangent
Ran the command here is the file I got
files.txt
files (1).txt
Here is the same file formatted for you
I had the same problem on windows 10 as well (no problem on my mac). To fix it I :
@JRobber That was how @LmKupke was able to get it working as well, so thanks for letting us know that unblocked you.
It appears like we have an uninstall/update problem with our VS Code extension, specifically on Windows. We鈥檙e continuing to investigate it, and will use this issue to track it.
@jrobber, the first install that had the issue- was that a fresh install or did you upgrade from an older version?
Are you by any chance using a vs code workspace? i'm having the same issue too, but i don't seem to be getting the fatal error issue, only that the agent is terminating. It seems to be working for me though if I don't use a workspace.
I'm getting the following error, and uninstalling and reinstalling as admin didn't help. I'm not using a workspace either.
[Client I] Did not find user settings at C:\Usersuser\.vs-liveshare-settings.json
[Client I] Passed version check for Windows: found 6.3.9600
[Client I] Installing dependencies for Live Share...
A fatal error was encountered. The library 'hostpolicy.dll' required to execute the application was not found in 'C:\Usersuser\.vscode\extensionsms-vsliveshare.vsliveshare-0.2.146\dotnet_modules\'.
[Client.Agent I] Agent terminated with exit code: 2147516547 and signal null
Hi there. If you are having the same trouble I did with VS live share preview the solution that worked for me is as follows:
This allowed me the sign in button at the bottom of VS Code
I get the same error.
@saraoneal did you follow the instructions above? In your case go to C:/Users/user/.vscode/exstensions/
And delete the folder ms-vsliveshare.vsliveshare
Then try to add the extension again and reload vscode
@saraoneal, can you please run the commands above to get the list of files in the extensionsms.liveshare directory? The install step is opposed to unzip and move some files and I want to figure out which step failed.
Yes, I followed the steps you suggested exactly. Here is the file generated from the command above.
Thanks. Looks like the dotnet runtime did not get unzipped at all for some reason. Can you please find the log file under %temp%\vsfeedbackvsrtclogs? The most recently modified file would correspond to the latest session.
That log file might tell us if it thinks it's unzipped the files or if something else went wrong
Here's the latest log file.
That log looks strange.. it says it's starting to install dependencies but no messages after that. One more request - could you please look to see if there's a file called install.lock in the extensionsms.liveshare directory ( the command above listerd only directories).
Yes, that file is there.
I've the same problem, and prior to try the suggested workarounds I post here the files that maybe you'd like to have for investigation:
20180220_114538_VSCode.log
files.txt
I've tried both suggested workarounds but without success.
Here is my last VSCode.log:
[2018-02-20 12:18:55.739 Client I] Did not find user settings at C:\Users\ncara.vs-liveshare-settings.json
[2018-02-20 12:18:55.745 Client I] Passed version check for Windows: found 10.0.17101
[2018-02-20 12:18:55.751 Client I] Installing dependencies for Live Share...
[2018-02-20 12:18:56.230 Client.Agent I] Agent terminated with exit code: 2147516547 and signal null
@LmKupke I think this issue should be reopened.
OK, thanks to @srivatsn I've found that my instance of VS Code was indeed a 1.20.1 version but a x86 one, so I've uninstalled it and installed the x64 version, and now the plugin do works.
These are the steps I've followed:
C:\Users\ncara\.vscode);C# plugin and restarted VS Code (optional, but this is what I did);VS Live Share plugin and restarted VS Code.On restarting, I finally saw the Finishing VS Live Share installation (downloading)... message and eventually the VS Live Share items on the status bar:

This solved my issue, hope this can help.
@ncarandini Eureka! I just tried reproing this and it happens 100% of the time using VS Code x86 on Windows. That appears to be the specific problem.
@LmKupke Which architecture of VS Code are you using? x86 or x64?
I can confirm that I am using the x86 version of VS Code. I can't upgrade at the moment, but will try soon.
@saraoneal Thanks for confirming that! We're going to prepare a fix for x86 VS Code on Windows, since we can verify that is a source of at least some user's problems, but it would be awesome to confirm that you are unblocked once switching to x64 VS Code.
@LmKupke Is it possible that you were using the x32/86 version of VS Code when you were hitting this bug, and you actually switched/upgraded to x64 when Live Share started working? When running the x32/86 version of VS Code, it will actually ask you if you'd like to upgrade to x64, so I just wanted to check if you happened to do that.
@lostintangent this absolutely fixed my issue! Thank you all so much!
@lostintangent Unfortunately I am unable to check now, because my work computer hard drive crashed. :(
I lost all my applications and data. However once I am situated I can try again and see if I run into the same problems others are having
@LmKupke @saraoneal @ncarandini We just published an updated VS Code extension that should resolve this issue (0.2.151). Apologies for the problem!! Let us know if you (or anyone else) running 32-bit VS Code are still seeing problems with this update.
Another employee at our office upgraded his extension and he can now sign-in and attempt to share as well! Thank you all so much for the help.
Great! Closing as fixed. We will re-open if anyone hits a problem here.
FYI, If any one is still having this issue, check your user settings. I had a user setting to hide the status bar. Ooops!
"workbench.statusBar.visible": true, is what you want.
Most helpful comment
@ncarandini Eureka! I just tried reproing this and it happens 100% of the time using VS Code x86 on Windows. That appears to be the specific problem.
@LmKupke Which architecture of VS Code are you using? x86 or x64?