-
Notifications
You must be signed in to change notification settings - Fork 511
Initialisation Error - Windows 10, new install of code and extension #1847
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
Thanks for the info! Can you also attach the logs here so we can get a better idea of what's going on? |
I've done this but the logs seem pretty empty.
|
Can you set the log level to "Diagnostic" and attach those logs? It should create a setting:
The link above has the full steps. |
There are no logs though. Whilst the argument suggests there should be a EditorServices.log file there isn't one.
|
@SwarfegaGit do you use an anti virus? We've received a lot of reports in the last version that antivirus has been getting in the way of PowerShell Editor Services starting up in the background. We have a fix that is pending a new release. |
Yes, McAfee Endpoint Security.
I am running the system version of VS Code by the way. |
This is fixed in #1837. Pending a new release which should happen today or early next week! |
I will dupe this to #1831. We've already got a report that says the fix worked. |
The extension fails to load the console. It takes a while before it times out with an initialisation error. The logs just show...
I can see people have had this issue in the past but they appear to be fixed on releases. This is a fresh install of Windows 10 along with Code and the extension. This is a company laptop though on Azure AD so something tells me they might have changed something.
PowerShell 6 will open fine.
Execution policy is RemoteSigned
Tried the preview extension but also fails.
The text was updated successfully, but these errors were encountered: