Mena Samer
Mena Samer

Reputation: 124

please wait while windows configures microsoft visual studio 2015 then error 2330

when i try to rebuild My Project Setup installer

in the first it try to configure as in This Image then this message in This Image

Upvotes: 0

Views: 496

Answers (2)

Stein Åsmul
Stein Åsmul

Reputation: 42136

Express: 1) Reboot, 2) disable anti-virus, 3) launch as admin and check. Then, if need be: 4) verbose log, 5) event logs. 6) Try on a virtual if you still can't get it working? Or secondary computer? Also 7) google exact error messages and check user comments. 8) Run general Visual Studio update?


Malware?: Run a full check for malware too? It is all over the place these days.


Locks?: A quick search seems to indicate a permission or patching issue of some sort.

  • You can try to run the tool with elevated rights?
  • You could have disk corruption - disk errors? Faulty ACL permissions? (possible)
  • It also just might be that your anti-virus suite has locked some file that MSI is trying to put back in place. You can try to disable it temporarily to see. Note that the file can have been quarantined as well (moved somewhere else).

Tip: Maybe check section: "A Deployment Mnemonic" here (down the page, yellow section).


Additionally: Please try the few hints here first. In essence: Reboot, get a verbose log file created, check event logs and try to log in as another user (generally only effective for user profile corruption issues, but can help):

Create verbose MSI log:

msiexec.exe /I "C:\file.msi" /QN /L*V "C:\msilog.log"

Links:

Upvotes: 1

herman.smn
herman.smn

Reputation: 1347

Not sure if this is the same error but you can give it a try. Just follow the steps from "How to work around this issue" section of Trouble installing other products after Visual Studio blogpost.

If there are indeed Visual Studio missing folders try to recreate them and see if this helps.

The behavior could just be a self-repair mechanism of the MSI installer of some Visual Studio setup modules triggered by the fact the related Visual Studio installer modules were incorrectly built by MSFT team (the MSI components were simply wrongly defined or sth like that).

Upvotes: 0

Related Questions