I got the Verification Code and I am able to enter it in the textbox. I can also press the Next button once, but nothing happens after that. The screen just hangs, I can not press any of the buttons. I tried several times, even let it try the entire night, but nothing happens..
On the previous screen I had problems with my proxy, but after setting the _JAVA_OPTIONS environment variable it seemed to work.
I am running the latest version (OVSMU-V1.1.0.005.exe) on Windows 8.1
Any ideas how I can continue?
Related
I installed Visual Studio Code 32 bit version (1.71.1) on a Windows 7 machine. I checked the box that said to launch it after I click Finish. The "wait" mouse cursor showed for a second or two, then nothing.
I tried double clicking the desktop icon with the same results. No error message. Not indication that it attempted to start. I did change the desktop icon to "Run as administrator" and that got me the prompt to allow changes to the system, but again, nothing comes up.
Any idea of what is going on? Is there a specific .NET version I need to have?
Yesterday, VSCode (1.67.1) decided that it was unable to start (crashes immediately) and spits out the error code -1073741818. I have the option to reopen or close but nothing happens regardless of the option chosen. Thought it might be an issue with the file/folder I was opening but no success opening any files/folders at all. Tried to disable GPU, disable extensions and re-install but all lead to the same error code. Tried to move to Atom, but, oddly enough, the same issue occurred. Discovered Atom and VSCode are both based on Electron and that Electron has previously had issues with Nvidia drivers (currently running 512.77) so I tried to install previous versions of the drivers that were working but no success. I finally gave up and moved the code to another system and everything works flawlessly.
So now I that I have some time, I am trying to figure out what went wrong and where to go from here. My uninformed, uneducated guess is it is driver related but I am not sure how to resolve it. I was able to successfully use VSCode earlier in the day with no issue. The system went into stand-by mode and upon return, the issue began. Any suggestions/guidance on where to start would be greatly appreciated.
VSCode Crash Window
Welcome to the community! I think this is caused by an corrupt installation of vscode, try to restart your computer and maybe reinstall vscode by going to, https://code.visualstudio.com.
If that does not help maybe try to submit an issue on the vscode github here: https://github.com/microsoft/vscode.
How to submit an issue on github:
Find the menu bar where it has multiple menus, it should have: "code", "pull requests" and "issues".
Click on "issues" button.
Click "new issue" to create an issue.
Then click "bug report" and enter details to file issue.
Once ready click submit issue to submit your issue in github.
Also, you'll need a github account to create a issue, signup here: https://github.com/
I hope this helps!
Please check if you've installed any additional extensions which may be causing the VSCode to crash.
My VS code keeps crashing when opening it
I had the same problem. First, it used to crash once every 10 minutes, then it started crashing 10 times a minute after a few hours. It just stopped working that day.
I don't know how it was resolved but it did automatically resolve.
I searched for the solution but the VS code on GitHub was already closed. If applicable take a rest and let your PC calm down also. Then if the problem doesn't get resolved, try contacting the developer team.
I have a really wired problem (or a bug) on vscode. I can "attach chrome" debugging totally fine usually,
but after some random time connecting to the chrome instance (may be a couple of hours or 8 hours, like I left it connected while I'm sleeping), it automatically disconnect the debugging,
then when I try to re-run attach chrome to reconnect it, for some weird reason it doesn't connect to the instance.
It's not a failed, it's not like "cannot connect to the port 9222", it's infinitely trying to connect showing the left up side blue indicator left to right.
This is my second time to encounter this weird problem. For the first time I even don't know how I solved the issue. maybe I just waited its reconnect for an hour or like that.
The first things I happened to think from the problem is simply its port conflict. So I checked vscode side's (I mean I use vscode in the remote ssh mode from Windows to Linux Ubuntu) port and process, used htop to filter port "9222" or process "chrome", but I didn't find anything stucking there. So I assume in the linux side the debugging process is exiting successfully.
So I did the same on the Windows side, I used resource monitor to check port "9222", no running process. If I re-open a 9222 debugging enable chrome, then it appears. closing, it disappears. It seems there is no problem here as well.
I then checked vscode's version. I was using vscode 1.64.2 so I side-installed 1.65.2 and 1.66.1 (the latest) and tested it. Doesn't work.
"refreshing the window" doesn't work. closing the window and re-open, doesn't work.
So what can I do?
Did you just install some new extensions in Visual Studio Code? I found that I had this exact same behaviour, "infinitely trying to connect showing the left up side blue indicator left to right", after I installed Karma Test Explorer and Test Explorer UI extensions. Once I uninstalled those extensions, debugging started working again.
I started having this problem a couple of months ago, I believe soon after I installed Visual Studio 2022. I am in the midst using VSCCode for an educational project (JavaScript) that will finish this weekend, so have mostly just been hoping VSCode would work until I finished. (I have not been using VS2022.)
The first time I had this problem, I was closing VSCode and a window appeared regarding some updates. After maybe 10 seconds I received a failure message. After that, I could not start VSCode.
I tried to uninstall VSCode, but it would not work. I tried to install VSCode from the main URL (Download for Windows Stable Build), but it would fail to install with a message about "Not being able to rename or write to a file".
I next tried the System Installer link on the /Download page, but I received the same message. I next tried the User Installer link on this page, and it worked. I could launch VSCode again, but the icon in the toolbar was just a white page instead of the VSCode icon.
I don't exactly remember when, but at some point, perhaps with manual updates from the Help toolbar in VSCode, the VSCode icon reappeared in the toolbar.
But then a few days ago, when closing VSCode the window appeared again regarding some updates, then the failure message, and then VSCode would not start. I tried the various download steps again, but only the User Installer would work. And again, just the blank page for an icon in the toolbar. So just leaving everything open for now!
After this weekend, I am hoping to fix this issue. But hoping someone knows that the problem is.
I am running Windows 10 Pro (up to date), and have the blue dot telling me I can upgrade to Windows 11.
Since VSCode is working, maybe I can do a complete un-install. Or perhaps upgrade to Windows 11, or maybe a complete clean install of Windows 10 or 11.
Has anyone else had this issue?
Thanks!
I have Visual Studio Code version 1.22.2 running on Windows. When working on Javascript code, it crashes and causes a blue screen with the following technical info:
STOP: 0X0000007E
mfeavfk.sys - Address <...>
I have a plugin for MS SQL and a beautify plugin installed.
I recently updated Windows and started experiencing BSODs every time I started VS Code. Here's how I fixed it - hopefully this helps someone else:
Open a command prompt and type the following command:
code --disable-extensions
If your computer doesn't BSOD after this step, then an extension is likely causing the issue.
Press ctrl+shift+x to open the extensions sidebar
Under disabled, uninstall any extensions you aren't using or don't recognize.
Restart VS Code, and see if it still crashes.
If step 3 didn't help, try removing all extensions and then reinstalling one at a time until you find one that causes the crash. Then repeat steps 1-4, this time removing the extension you identified as causing the crash.