VS Code has been trying to update for a few days now. It opens the innoupdater, but the updater never works.
Today I force stopped the updater from task manager and now my VS Code is gone (The VS Code icon is gone). It's showing the below error every time I try starting it.
windows cannot access the specified path you may not have permission
The innoupdater is also not working anymore, even if I reinstall. I am not sure How I can get my setting back.
You can safely reinstall vscode. Settings preserved even after uninstall in %USERPROFILE%\.vscode.
Also, you can use vscode built-in sync services or extension
Related
The code::block can't build file everytime after I restart my computer. It will show that there is error like this:
enter image description here
or "A debugging checking in this application has failed" like this and sometime it even can't allow me to open a new project:
enter image description here
But the strange thing is that when I first download the app and before I turn off the computer, it can build and run the same programe. This situation only appears when I turn off and turn on the computer again. However, when I reinstall the app, it can build and run the programe.
Can anyone please help me, I need the code::block tomorrow and it is impossible that every time after I turn off the computer I need to reinstall it.
I have tried to reinstall it, and open project in different way.
enter image description here
Tried installing and re-installing but of no use.
Every time it says Keyboard Shortcut Conflict for Ctrl+P. But I can't do anything about it as it doesn't open up. I do have keybinder but I don't know how to sort this out.
Inserted Screenshot of exact error message showed. I even tried installing nightly builds but the same error message pops up. every time.
Deleting the user files (only the "keybinding" files) in the directory below then restating CodeBlocks will help if the problem is just because a key conflict:
directory: C:\Users\YourUserName\AppData\Roaming\CodeBlocks\
Depending on the CodeBlocks version, the file names may be something like; cbKeyBinder10.ini, default.cbKeyBinder10.ini, default.cbKeyBinder20.conf
Important note: To be on the safe side, instead of deleting those files immediately, just rename their extensions as .ini_bak or .conf_bak. If this procedure solves your problem, you can, then, delete the backup files. If not, you can rollback your changes by returning the extensions back to their originals.
Hope someone can help me here .
I have no further information other than that at a later stage in setup the whole process hangs showing install_confignonrc_cpu64
I am unable to cancel out of it even , the only way was to kill it .
Is there any solution for that ?
My problem was that the installer tries to download Microsoft R Open , if you have a slow connection you will see the installation freeze for a very long time without any progress bar updates or so .
I fixed the problem by deselecting all R components since i dont need them then the installation went smooth .
just had the same problem which is why I found this question.
Fixed the problem by closing the original media install menu window (where I'd selected "New SQL Server standalone" which is the first option).
The install window then carried on.
Just leave it "Stuck" - it is doing a Download in the background, I left the PC for a couple hours while doing some errands, and then..boom- All set.
I have faced same problem with you, the simple way that i have find is turn on Windows firewall then wait a minute after that it will auto complete setup success. Hope this work in your case .
Thanks,
Cuong.
Disable and stop the windows update service and then start the installation. After the installation is complete put the service back on.
SQL Install gets stuck on sqlrsconfigaction_install_confignonrc_cpu64 (SQL Server 2016 using standalone installer, also when installing on Azure VMs)
Resolution:
Stop the install (Taskman -> Kill Process)
Open regedit
Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\
Add New Key Called: AppCompat
You should have this once added:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Policies\Microsoft\Windows\AppCompat
Add New DWORD entries as stated below to the AppCompat key:
DWORD: DisableEngine Value = 1
DWORD: DisablePCA Value = 1
DWORD: SbEnable Value = 0
Check the following location as the above key you added should also be here:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\
Restart the installation.
I closed everything and rebooted. Not sure if maybe having Visual Studio open or something else prevented it from installing, but it got stuck.
i have a solution
it has 2 projects inside.
there are an exe and a website.
the issue occurred when clicking F5 to start the debug process.
when i have set the exe to the default StartUp project. The exe can run normally, and the break point can be reached correctly.
however, when i have set the website to the defualt StartUp project. The website can be launched, however the breakpoint cannot reach. also the version isn't the latest one, it looks like it is loading the last succeed version (no error and warning too)
I have to right click the website project and click start new instance in the Debug every time I have modified something!(which is very troublesome)
Thus, I want to know why my F5 isn't equal to the Start new instance, as it is working normally in the other solutions.
I fixed that but the below procedures after struggled from extra many clicks compiling experience.
the cause is that there is unknown reason that the build checkbox isn't checked in the configuration manager. simply check it and everything looks fine again...
hopefully it can save someone time who suffered from this issue in the future
I have a very simple VS2005 deployment project that aims to install for all users on a PC.
All the application files are written to %Program Files%\MyProg. A shortcut is created in the start menu and the startup folder. No registry settings or anything else are created. I have set
'InstallAllUsers' to true.
The created MSI runs fine and installs the software. It works without any problems when running under the user account from which it was installed.
When logging in as another user, the start menu and startup icons are present. It attempts to launch the application however an installation window pops up and states that 'the feature you are trying to use is on a network resource that is unavailable.' The installer will only proceed if pointed to the original MSI file.
Why does this happen? I want my application to be installed completely for all users when it is installed by a single user.
edit: Solution
I was getting similar event log messages as shown on this page. In my case it turned out to be as simple as ensuring that the User's Program Menu had its 'AlwaysCreate' attribute turned to false. If it was true, windows would try and recreate the folder when a new user logged in. This somehow required the invocation of the installer and thus resulted in the 'please insert the installation media' prompts.
It is actually kind of hard to say without some more information. I would recommend checking on the rights in the installed folder (seeing if only the one who installed it has rights) and also checking the file list for the directory (to make sure VS didn't automatically place some files in the user profile). Let me know what comes out from those two steps and we can try to keep digging if that didn't shed any light on it.
Keep in mind chances are this is most def not specific to Visual Studio, look at this MS support article here where the same message is coming back for office.
I know this is an old post but I thought I'd add another cause and solution in case the above didn't work for you.
There is a bug in VS Setup and Deployment Projects which results in registry values being entered into HKCU instead of HKLM irrespective of the InstallAllUsers property being set to true.
You must use Orca msi editor to change the registry root for "DesktopFolder" and "ProgramMenuFolder" from either 1 or 2 to -1. The issue cannot be resolved via VS.
http://www.qa.downappz.com/questions/vs-2010-deploys-per-user-features-during-install-which-require-access-to-install-media.html