-
Anonymous users2024-02-081. Make sure the installation package is correct.
First of all, we have to guarantee that there is no problem with the installation package of VS. Here we recommend going to the MSDN official website** VS2013 installation package, instead of going to some small sites**.
On the MSDN official website, we find VS2013 in the development tools column, select the corresponding version, and then click on the details, you can see the hash code of the installation package (that is, the string after SHA1).
After installing the package locally, use the hash verification tool to get the hash code of the installation package, and compare it with the hash code provided on the package (note, don't think that the source is correct, the file after the file must be error-free, and some tools will have a very small probability of error).
End 2. Installation and repair.
If it is true that there is no problem with the installation package, it is possible that there was an error during the installation. Let's take Windows Repair Install VS2013 as an example to illustrate how to do this.
First, close VS2013. If you previously installed it from a virtual optical drive, eject the installation package from the virtual optical drive.
Open the Command Prompt as an administrator.
Enter the cd"c:\programdata\package cache"Enter.
Then enter del f s *msidelete /f /s *.cab, enter. After making sure that all delete commands are executed, close the command prompt at the Acacia Rock Bridgehead.
Here's Microsoft's official explanation: If the installation fails, the installation cache may have been corrupted. If you want to fix the installation, you need to delete the wrong files (my jujube has personal experience, and the repair installation without deleting these files is invalid).
To ensure a successful repair, it's a good idea to reboot the system to completely eliminate the factors that caused the installation failure before (as there is a good chance that a hidden process is interfering).
After restarting, right-click the mouse on the installation package (ISO disc image file) and select Mount.
At this time, the installation package will be automatically loaded onto a virtual optical drive (I'm here *** drive h:) and open the files in the installation package. We double-click on the installer vs.
Once the installer starts, we can fix it by clicking on the "Repair" button in it. As a reminder, you should not open other programs or perform other operations during the repair period.
After 30 minutes, all the components were finally repaired perfectly!
-
Anonymous users2024-02-07Solution:1computer system.
2.If it doesn't work, use the 'computer to manage Mingzi's house.'
Or '360 Guardians.
The 'computer clinic' inside is functional, try to fix the VC++ components.
3.Based on the above, it is still possible, it should be a problem with the vs2012 installation package, re**. tips: win7 64-bit** install 32-bit vs2012 no problem.
-
Anonymous users2024-02-06Open the installer again and select Repair.
It's not much of a difference, in my opinion, what I see and feel is that the C disk is much smaller after the upgrade, and it won't affect the operation if you don't install it, it's just a collection of all previous updates, and you will be prompted to install it later.
First, the installation method is wrong, second, the model is not supported, third, the network connection is not normal, fourth, the memory is insufficient. >>>More
There is no big taboo in this, just to express the niece's condolences and regrets. True. >>>More
PBP is the format used for folder-based games, and generally, those are emulator games, such as PS games. >>>More
So you have to know your file format when you press it.
Method. Open the file properties and you'll see the file format. >>>More