Okay, I have searched for a solution to my problem on the internet and could not find an answer to my specific problem. When I am trying to install something that uses Windows Installer (msiexec.exe) the installer never makes it to the progress bar. When I run task manager and look at the msiexec.exe they are both running at 0% cpu, and not doing anything. (Both meaning the 32bit and the 64 bit versions). The setup program is stuck on "Setup is preparing the InstallShield Wizard. Please Wait."
I don't have any other installations running, and I have waited hours longer than it should have taken to initialize, and install. So waiting will accomplish nothing.
Sometimes when I terminate the 32bit msiexec.exe, the installShield would continue but sometime during the installation it will hang with the 32 bit msiexec running again at 0% (zero percent) CPU usage. And then I would end the 32 bit process again and it would continue onward, until it hangs again but this time there is no 32 bit msiexec in the Task Manager. And if i terminate the 64 bit MsiExec the program would alert me saying "Error 1719. Windows Installer service could not be accessed. Contact your support personnel to verify that it is properly registered and enabled."
The Windows Installer Service is registered and Enabled it only pops up when i terminate the 64 bit MsiExec that is doing nothing. Sorry if this is too wordy but I am putting in my specific problem. All other solutions were for those whose msiexec were running at 25% - 100% cpu, My problem is that it is doing NOTHING, it is running at ZERO % CPU
EDIT: I have found out how to fix my problem. it seems that the Volume Shadow Copy service (which is what windows uses to make backups of.. well.. windows) might be hanging.
My solution was to open taskmanager and click services. look for VSS right click it, click restart. Then I ran the installer again and it worked!!!
Related
For over a month now I've been experiencing problems with VS2017 on my home PC. I even tried submitting the feedback to Microsoft. There's more info about the problems I'm experiencing there.
The problem:
The gist of it is that VS is eating RAM like crazy. As soon as I start opening files, adding new files, using IntelliSense, building or (especially) debugging, the RAM usage skyrockets.
After that it's only a matter of time before the VS crashes and restarts without any error message. Though there are numerous error messages throughout these breif ~20min I have with each session.
Additional details I observed:
Doesn't happen with Python projects, as these don't have to be built constantly. It might be eventually happening if you debug a lot, but I didn't have the chance to check that because most of my Python coding is debugged on an external device
Size of the loaded solution doesn't matter;
UWP and WPF seem to crash the most. Console Projects take longer to crash.
Also affects .NET Core;
It doesn't matter which version of .NET Framework I use;
VS2015 worked perfectly, but I don't have it anymore after the format
What I already tried:
I reinstalled VS;
I refreshed Windows;
I reinstalled Windows;
I checked my drives and RAM for issues - none found;
I switched from Community to Enterprise;
I tried disabling extensions;
I applied some shady hotfix I found somewhere;
Finally, I installed Rider which seems to be the best solution as of now. It still lacks many important features, though.
Is there anything else I can do/try/check? Did anyone experience (and fix) a similar issue?
Cheers!
You get a System.OutOfMemoryException, this means your Visual Studio runs out of free virtual address space (4GB on 64 Bit Windows for the 32Bit Visual Studio because Visual Studio is configured to be large address aware and MS refuses to release VS as 64Bit program which would fix this issue).
To analyze the memory usage, you need to run WPRUI.exe (part of Windows Performance Toolkit (which gets installed by VS2017) for some scenarios, if not, install it on your own), select Reference Set (Note: expand the Resource Analysis entry first to see all options).
and click on Start. Capture the memory usage grow for some 100s of MB and click on Save.
Open the generated ETL with the analyzer (WPA.exe) and analyze what the process devenv.exe is doing.
Also zip the ETL + NGENPDB folder (important) as zip and attach it to your bug report so that Microsoft can analyze it.
Pretty self-explanatory. Whenever I try to press 'play', as in the green play button to try and test run the app, my ENTIRE computer freezes. (Otherwise Android Studio seems to work fine, if a bit laggy.) I can't even move the cursor--even if I wait for more than fifteen minutes, it's frozen. The only option is to shut down the entire computer using the button on the outside of the computer. In my research, I couldn't find anything else with the same problem, let alone a solution.
I've tried installing an earlier version of android studio, but it did not help. Same problem. I'm thinking I might have to do a fresh install of Ubuntu and see if that works, which is a pain because I have GBs and GBs of data on this one. Help?
Specs: Running an Acer Aspire with 8GB of RAM, 64bit, Intel® Celeron(R) CPU N2840 # 2.16GHz × 2. Can't check the RAM at time of the error, because the entire computer gets frozen.
I have been running a trial version of youtrack on my windows pc couple months back. I would like to get rid of this.
It seems like there is a javaw.exe process with Username JetBrainsYouTrack consuming almost 1GB of memory on my computer. The program restarts with a restart of computer. There is no signature of an installed JetBrains program in control panel.
How do I remove this program from the computer?
Is there a folder in which the program has all of its files etc..?
I imagine there will be, if so, there will probably be an uninstall executable that you can run.
I've just downloaded Eclipse on elementary OS and attempted to launch it. After doing so, I saw the loading screen for a few seconds before it disappeared and left me with the desktop. Since then, my computer (an old Dell with 4GB of RAM and an Intel Core Duo) has been very unresponsive and the disk activity indicator is almost constantly lit up. I've been looking at the desktop for around 30 minutes now! How can I solve this problem and launch Eclipse?
EDIT: Running eclipse -clean from the command line produces the following error: The org.eclipse.m2e.logback.configuration bundle was activated before the state location was initialized. Will retry after the state location is initialized.
First, you might review your installation steps. If nothing is obviously wrong, check the following:
check for any error logs
check that you're using the proper Java version
make sure that there's enough memory allocated for Eclipse (see the eclipse.ini file)
as a last resort, try reinstalling it
See also the following guide for installing on Elementary OS: how to install
If that's not working submit more details of your specific problems.
NOTE: You may have to find the right Java and install it "by hand" rather than relying upon the distribution's package manager. You can "point" Eclipse at the right Java by editing the .ini file.
Some related links are as follows:
a similar symptom related to multiple screens and/or corrupt workspace
General trouble-shooting related to your issue and symptoms
First off, I think I've been to every website and forum there is that's discussing this issue and I've tried many different things. I'm at my wits end. This is the dumbest thing and I just want to start coding again!
I'm using Visual Studio Express 2012 for Windows Desktop. I have a x64 project I'm trying to run in Debug mode using the local windows debugger. The only external library I'm using is that of which is required to run DX11.
I attempt to run my program and it freezes. A window pops up saying "A remote operation is taking longer than expected."
I click Terminate and another window pops up asking if I'd like to terminate the remote session. Why yes, I would.
Then it says, "Unable to start program (my path leading to my .exe). The network connection to the Visual Studio Remote Debugger has been closed."
To my understanding, because Visual Studio itself is a 32 bit application, it needs to use the Remote Debugger to compile to x64. Is that correct?
Regardless, I'm still failing to see where that would break down. I've ran several repairs on VS and upgraded to Service Pack 2 (or 1, whichever is the latest).
I've ran a windows repair and uninstalled any VMWare type stuff on my computer. I'm not using a VPN.
I've even copied msvsmon.exe from my laptop (working instance of the project) over to this computer and still no luck.
I'm about ready to Nuke my OS and do a clean install on everything. sigh
Found the problem. It wasn't Windows Firewall like other threads describe. It was my internet filter. I guess it decided to try and block msvsmon.exe because it was using the network. Adding it, along with WDExpress.exe to the application exceptions list did the trick.