Fiddler 4 is not opening up. I tried opening it, running it as an administrator and troubleshooting.
I installed it last week, and nothing was wrong then. I could use it until yesterday, when it wouldn't even start up. I didn't have any errors until it wouldn't start up.
I am trying to open it from cortana, the shortcut and in the programs.
Related
This is a strange one, I've had it occur a few too many times and it's difficult to give a title to, but recently on a number of occasions when I try to open one of my existing sessions (VM or Server doesn't matter) the session doesn't open, it's just a black terminal screen with nothing on it, but my Windows task bar disappears, sometimes it ends up in the MobaXterm terminal window sometimes it doesn't. But if I then try to close the MobaXterm window I get a pop up on my PC for a shutdown, and the only way to close this window is to shut down my PC.
I am running a windows 11 PC, with MobaXterm Home Edition 22.2, and have seen this in 22.1 also. Not sure which earlier versions I was running before I encountered this problem or which version it started with.
Is this a known bug, another of my colleagues has encountered this also? Is there some setup I'm missing that could prevent this?
I just opened Visual Studio Code and this error is displayed at the bottom right of the screen.
The isort server crashed 5 times in the last 3 minutes. The server will not be restarted.
My code can run normally without any problems, but the message keeps popping up every time VSCode is opened.
How to solve this error?
I figured it out that isort is an extension in Visual Studio Code about sorting imports in python, which is not necessary to me. I don't even remember installing it myself.
Therefore, I just uninstall the extension. As a result, the error goes away (of course).
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!
Lately, after I have been using VSCode for some time, opening and closing it repeatedly, I was surprised to see, in Process Explorer, a lot of wsl.exe processes. As it looks, 4 or 5 processes were started by VSCode each time I opened it, but were not terminating when I was closing VSCode, so I ended up with a lot of them (there are only 5 in the image, but actually there were several dozens).
I think this has something to do with the following dialog box I see (almost?) every time I open VSCode
(which I was just closing since I am not interested to install these extensions).
Does someone know how to disable the launching of these processes? I had a Docker extension which I uninstalled, but this behavior persists.
Ok, so the culprit is not this something which launches the dialog box (I still see it), but it appears to be the following setting (when checked)
After unchecking it, I don't see now any wsl.exe processes launched when I start VSCode.