I installed 2017 and used it for some time (months). After one of the updates, I started having trouble in the file browser window not navigating to other folders without hanging. I can't navigate or choose a file. the app is hung here. I have left it up for several minutes and it stays hung there. I have to kill it from Task Manager in the current version; in prior versions it hung the system and I had to power off. I saw similar problems posted and a reply that indicated it was reproduced and would be fixed. I starting using VS 2015 again in the meantime. That was a few release ago. I had hopes that the most recent one (now on 15.7.3) might fix it since it was fairly large. It made me have a different issue in the same dialog. Now it is blanked out and only VS 2017 is hung. That's a little better since I don't have to restart my system every time I try to run it. But I really need to move to VS 2017.
Any suggestions would be appreciated. I have uninstalled and re-installed several times and tried uninstalling and reinstalling the more recent .net versions.
Windows 10 Enterprise, kept current with Windows Update, 32G RAM
On trying to browse for a solution, this comes up.
Related
Environment
I'm using Visual Studio 2019 version 16.7.2 on a Windows 10 VM, hosted by Parallels on a brand new MacBook Pro. The VM has eight virtual processors and sixteen gigs of RAM.
Nothing other than Visual Studio is installed on the VM.
What I'm trying to do
I'm trying to compile a Visual Studio solution consisting of seventeen projects. The projects are relatively small. They're all C# console applications or DLL libraries targeting .NET Core 3.1.
Problem
Typically a Rebuild Solution executed after a Clean Solution takes place in about ten seconds. A typical Build Solution (Ctl-Shft-B) that I execute throughout the day takes place almost instantaneously.
But occasionally, in maybe one build out of five, building the solution/projects causes VBCSCompiler.exe to consume 99% CPU usage and freeze up for approximately thirty to forty-five seconds prior to executing the build. Once it starts executing the build though, everything completes normally. This long delay which occurs time and time again is making my development cycle terribly frustrating. I'd like to find a way to eliminate this delay.
What's Changed
The build executed fine on my Amazon Web Server Windows 2016 m4.xlarge VM. I recently switched over to the Parallels VM to save money. That's when the problem began.
Again, I want to reiterate that the Parallels VM is clean. Nothing other than Visual Studio is installed there.
What I've Tried
The following tactics were applied to no avail.
(1) I turned off the Defender real-time virus checker.
(2) Based on the information in this post, I went to Tools | Options | Nuget Package Manager | General, and unchecked 'Allow Nuget to download missing packages' and 'Automatically check for missing packages'
(3) In Tools | Options | Projects and Solutions | Build and Run, I set the maximum number of parallel projects builds to one.
(4) Based on an answer to an unrelated question, I learned that I can view more information about the build process by setting 'MS Build project build output verbosity' to Detailed. I did so. I waited for the freeze to occur so I could examine the last line of output prior to the freeze. It reads as follows:
Using shared compilation with compiler from directory: C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\Roslyn
This line always appears immediately before a freeze.
(5) Based on the output above, I Googled 'shared compilation' and discovered this post.
As a hobbyist programmer, the discussion that took place there, as well as the link in the accepted answer is well above my pay grade. It's unintelligible to me. If the answer lives in that post, I can't decipher it.
Any ideas on how to solve this intermittent freeze? If I can't figure it out, I'll have to assume it's something about my Parallels Windows 10 VM that's causing the problem, and revert back to developing on an Amazon server. I'd prefer to avoid that if possible because of the added expense.
Thanks for your consideration.
Best,
Festus
Since a couple of days whenever I start VS 2017 and open a project, a message box pops up telling that "The 'HopexPackage'
did not load correctly..."
.
When I look at my extensions, I can see that some Hopex add-in is really installed there:
When I uninstall the add-in, I need to re-install a couple of other add-ins (that seem to be blocked by that hopex). But when I start VS again, it is there again. I did an exhaustive search in the file system and the registry, but could not find anything relevant.
It behaves like a virus. Do we have specific VS viruses nowadays?
Perchance does anybody know this behavior or/and a recipe against it, other to completely re-install the VS?
Thanks.
I used to deal with this when I was working with Adobe AfterEffects. It was (and maybe still is) so buggy that it could crash at any moment. So instead of fixing their buggy code-base their developers added a feature that would periodically auto-save all solution files into a separate (copy) folder. So after a crash you could recover some of your work. (Mine was set on auto-save every minute.)
So I've recently switched to using Visual Studio 2017 to develop my C++/MFC projects. (Before that I worked with somewhat older VS 2008 that used to crash very rarely.) But now VS2017 crashes pretty much every day. And if I forget to click save, it literally takes down last 10-15 minutes of my work, if not more.
I tried reporting this to Microsoft (back in summer of 2018, 6 months ago.) Some of my reports were either closed right away when they needed more proof and I didn't have time to deal with their laziness to read my entire post, but some that were accepted are still open and were never fixed. So I'm done submitting bug reports through that portal.
My only recourse at this point is to ask if there's an auto-save "feature" in VS2017, similar to what Adobe did to their AfterAffects?
Anyone wants to crash it right now? Here's just one bug. Create new project -> Visual C++ -> MFC/ATL project -> MFC Application. Then go to Resource View -> Add Resource -> Accelerator. Then click on "None" where I pointed with an arrow:
Is your VS2017 still running after that?
You can find a plugin in the market that does the job.
https://marketplace.visualstudio.com/items?itemName=fluffyerug.Autosave2017
"Auto Save File" extension has more installs and better reviews than the extension from fluffeyrug.
https://marketplace.visualstudio.com/items?itemName=HangjitRai.AutoSaveFile
I have Windows 10, fully updated.
I downloaded and installed Visual Studio Community 2015 last week for the first time, (previously programmed in Code:blocks, still installed) and selected custom install to allow for C++ and Python programming.
Installation ran smoothly, but VS always fails on launch.
On first launch ever, it said it was setting things up for first startup; asked me for sign-in which I did, at which point it briefly showed something about my profile before saying 'An error occurred while starting for the first time. Please restart Microsoft Visual Studio'. Imgur images of all dialog boxes here, including parts of a processmonitor log I estimated to be around the general time of the error.
Closing and restarting several times didn't help.
Uninstalling and re-installing didn't help.
Rebooting didn't help.
And uninstalling, running Ccleaner's Cleaner and Registry Cleaner, rebooting computer and re-installing VS didn't help either.
Repairing the install from Programs also didn't help.
I managed to find the exact same error on Google Search for VS 2013 but the only solution was where one person got a completely new OS and re-installed VS on that.
I tried the other suggestions they had including running:
devenv.exe /safemode
devenv.exe /resetskippkgs
devenv.exe /resetuserdata
devenv.exe /installvstemplates
devenv.exe /resetsettings
the first 3 took me to the same sign-in screen. Regardless of signing-in or not, or running VS from the Administrator Profile or not, these option always give the same failed on first startup error.
Installvstemplates gives an error saying the operation could not be completed, but /resetsettings finally got me into VS.
That's about all it does though, I can go to the home page and access options/menu buttons, but signing-in makes it crash and reload again (but it does sign me in and take me to the home screen)
Signed-in/not and Administrator or not, VS crashes on opening a new .cpp file.
When I click Start a New Project I get "Error loading type library/DLL.(Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)). Closing VS and trying to open it normally from start menu still always throws the original error, despite working if I open it via /resetsettings.
I've also checked [HKEY_CLASSES_ROOT\CLSID{73B7DC00-F498-4ABD-AB79-D07AFD52F395}\InProcServer32] in Regedit and found it is apparently correct.
I also used devenv /log to generate an xml file of the process when I open it.
Just to mention I have .NET Framework 4.5-4.6 installed with VS as well.
Looking forward to any advice.
So, for anyone else getting the same problem, I haven't gotten any other advice, since this post.
If you're still having probs # this point the only real solution seems to be a clean install of your OS .
I can confirm it solved all my issues, with VS + some OS problems I wasn't aware of . I can only assume they might've been related, good luck.
This question actually is an implicit answer, since I could fix the problem in the meantime for myself. But I wanted to publish my experience, since some other developers might have a similar problems.
The problem:
I am using VS2010 prof SP1 on Windows XP SP3, pure C++ only. (AntiVirus software present).
Since some days Intellisense - which is quite helpful under normal conditions - does not work anymore.
Things tried:
created a new simple console application. -> Intellisense still not working.
resetting VS-Settings by means of Tools/Import & Export Settings/Reset. -> Intellisense still not working
Changes to option settings in Text-Editor/C++/Advanced inclusive logging did not help.
-> Intellisense still not working
There was actually an interesting observation:
Intellisense normally creates a directory 'ipch' in the solution directory to store intermediate files. In my solution folders it disappeared as soon as the solution was opened. When I created a folder 'ipch' and opened the solution Intellisense removed the folder again - strange.
The final fix:
During the last week some new Windows updates were installed. I noticed some other unusual behaviour of my PC as well. After having created an image of my PC, I decided to
uninstall Windows updates from 2013-09-11 (4 packages) and one update from 2013-08-28.
(unfortunately I did not note down the KB-numbers)
AND: out of a sudden Intellisense is working again !
Maybe this report could be helpful for some other persons.
Automatic Updates are now disabled on my PCs.
Confirmed 100%
Microsoft Visual Studio 2010 Version 10.0.30319.1 RTMRel
Microsoft NET framework 4.0.30319 RTMRel
Microsoft Windows XP Professional Version 2002 Service Pack 3
Intellisense stops working after installing KB2876217.
Intellisense is back after removing update.
I had the same problem and also had the idea that one of the Windows Updates is buggy, so I can confirm your report.
I tried to uninstall them one-b<-one and found the "bad guy":
KB2876217 destroys intellisense for VS2010 under XP SP3.
A supported hotfix is available from Microsoft to fix this issue. Check at http://support.microsoft.com/kb/2526044/en-us
Actually, it may not be such a good idea to uninstall update KB2876217. Instead, install Visual Studio SP1 update (if not already installed) and then install update KB2526044. I have tried it before and it does work...