Visual Code update failing locked code.exe on windows - ide

When Visual Code asks for a update it fails and says code.exe is locked, I check with lockhunter.
I tracked the issue to the task manager, and process id 4 memory management I think is using it. I have to restart the pc to get the file deleted and I need to download visual code again. All my colleagues have the same issue.
Any ideas on how to solve this?

I found out it was the company software blocking the update. Seems silly.
Please close it.

Related

Visual Studio VB: The Operation Could Not Be Completed

I was using Visual Studio 2022 edition and it was working fine last night. When I tried to open it this morning, it gave me an error:
The operation could not be completed
I don't know what happened. I already have ran into few suggested solutions and nothing seems to work. I have tried:
closing and restarting the Visual Studio;
restarting my computer; and
deleting .suo, which I don't have unfortunately. I must also mention that upon closing the error message, I received another message:
Value does not fall within the expected range
Just in case they're connected problem. Any ideas?
It might be some type of corruption of files or something. Try reinstalling it to fix the files. Also make sure to turn on sync so your extensions and theme don't get lost.
#Jimi 's answer from the comments solved this problem.
With VS closed, remove the hidden .vs folder which is inside the main folder of your Solution. Then, for each Project, delete the content of the obj folder. Open the Solution in VS, right-click the Solution in Solution Explorer and clean / rebuilt it (clean may seem redundant at this point, but there's a reason for it)
In my case (VB programming) I had to go to Extensions->installed in the menu and enable: Web live preview. This seems to become disabled at new update.

C# application runs in the background as a process now i cant build the solution and cannot even kill the process

I ran into a very weird problem today with my C# application. I downloaded it today (from a trustworthy source my classmate sent me back the program we do together) At first when i tried to build and run the application, the whole visual studio got frozen and the app didnt even appear. After a lot of trying this problem just disappeared all of a sudden. However, now I cannot even build the solution, because I get the "unable to copy file because it is being used by another process" error message. I checked the task manager and the program runs in the background. I cant kill it because I have no access to do that(access denied message), I cant do that with a terminal command either(Because the terminal says this exe file is not running) and what is more even restarting my pc 2 times didnt make it disappear. It is no more in the processes after a restart, but i can still see it in the details view of the task manager.
I just have this program running in the background literally forever now?
Someone could explain me what even happened and if there is any way to solve it? I could even code (and build) the program for a while!

Visual Studio form resolution problem in editing mode

I'm on a VB.Net Winform project and I have encountered a strange problem with my IDE Visual Studio 2019.
When I double click in the solution explorer to open the form in visual editing mode, it shows up but with a wrong resolution, the form and everything in it becomes far bigger than it should be. But when I run the project in debug mode, the runtime resolution is normal.
I do have two monitors but I never had this issue before, it would be great if someone knows why and has a solution for it.
Problem was solved after a reboot. I think it was a pending windows update who caused this . Very often, a pending windows 10 update causes a problem, I've experienced the blue screen, wifi connection failure, and this time a resolution problem. Intentionally or not, it forces users to restart the computer to apply the update. Hope this can serve other people.

WiX Toolset - Handling the case of running the installer again after it's been installed

I have a custom bootstrapper (C# WPF) and it works well enough. If the installer gets run from the command line after it was installed, it brings up a window allowing the user to select if they want to modify, repair or uninstall. So far so good. Modify mode starts the UI which ends up calling Bootstrapper.Plan(LaunchAction.Modify). The problem is that if I call it from the launcher UI it immediately complains that a prior install requires a reboot.
I have not found any good examples on what this should do. Even the WiX mailing list came up blank.
Any ideas?
It would be helpful with the screenshot for that reboot message - just to get a feel for where it might be coming from and to get a literal string to search for. Did you have a look in the WiX source code yourself btw? (WiX 3.111 branch)
I started writing a lot of stuff about reboots. Not good. Maybe just some questions instead:
Does this happen every time you invoke modify and is it reproducible on more than one computer? Or maybe it is just Windows Update acting up on a problem computer?
I assume you have rebooted the computer where you see the problem and you see the problem again when you re-launch the bundle?
Do you schedule any reboots inside your MSI files during the initial installation?
Either using the ScheduleReboot action or a custom action which schedules a reboot with a call to MsiSetMode (for example)?
There is a long explanation here why such reboot-constructs cause problems, but that may be besides the point. Essentially badly configured reboot-constructs can trigger spontaneous, unexpected reboots without warning when packages are run in silent mode (plus other problems).
Could you try to run the test VBScript found in this answer: WiX behaving badly on XP machine with windows update issues in order to check if the script reports a reboot being necessary?
Other than that I guess you could try to run Burn yourself in debug mode (not sure how much plumbing that would be to get running) or perhaps first try a ProcMon.exe session to see if you can see something obvious. The latter should be quick to do?
There are some registry locations you can hunt down to see if you can figure out what triggered the reboot warning. Get-PendingReboot-Query. And a similar PowerShell script.
So in the end it was user error. :-( O well. I did learn a lot about how to figure out how Windows checks for the need to reboot etc.
The issue was simple in the end. During the modify run it was uninstalling, then reinstalling a number of services. The problem is that when it runs (seeing as you have to set it to repair to get it to work) it copies all the files again and the services were still running at the start of the install. The fix was to uninstall anything that might lock a file before the actual file copy starts and that solved the issue for me.
Thanks for your help guys, all the info helped me look in different directions until I found the issue. Awesome community as always!

Compile error in VS.NET 2008 (VB.NET) that I can't get rid of!

I can't shake this error when compiling my Visual Studio.NET 2008 solution. The project that's generating the error is a VB.NET Web Application in a 12 project solution (mixed types and languages).
I've tried all the tricks I can find on google, and the obvious of removing the directoy and folder manually.
I'm running Vista Business 32 with VS.NET 2008 SP1. This just started happening out of the blue today and I've rebooted a bunch and even re-applied SP1 for VS.NET.
Any ideas or has anybody seen this?
vbc : error BC31019: Unable to write to output file 'G:\Projects\TCA.NET\TcaNet\WebUI\obj\Debug\TcaNet.WebUI.pdb': Unspecified error
Update:
After thinking about this and not finding any solutions from answers or via the Internet, I went ahead and moved my entire solution to my C:\ drive vs. my G:\ drive (both are local). Doing this fixed my compile problem for some reason.
I had the same error a few weeks ago when I was compiling on my server from my laptop. Turns out that if G: is a network drive, this could fail. Microsoft have said that fixing this is not a priority, and that there's much better ways of doing things (such as source control). For a one-man project though, it's a pain.
Restart IIS on local.
If that's not the issue then, install Unlocker and try to delete that pdb file when you get the error, Unlocker will tell you which process is holding an open handle to that file.
I have found a list of thing to try to fix your problem :
Zen-turkey Fix list
Hope this help!
maybe it is a dependency problem. check the build order of all the projects..
sysinternals tools should be of help here. using process explorer, are you able to find out if any process is locking this file? another useful tool is process monitor. after applying a filter for the pdb file, capture a trace of all file access activity..
It's probably bug in VB.NET compiler. The error message is incorrect, the real problem is missing file referenced from the project file. For example .vb file.
In my case, I found the missing file and added it, then devenv compiled fine again.
Someone reported that to MS here
Although it is very old thread, but I got this error today and the following link solved it. Hope it help someone reading this.
VB.NET .pdb fix
After thinking about this and not finding any solutions from answers or via the Internet, I went ahead and moved my entire solution to my C:\ drive vs. my G:\ drive (both are local). Doing this fixed my compile problem for some reason.
I had this in Visual Studio 2005 except it was Error 1. I restarted my machine and it fixed the problem.