An error occurred generating a bootstrapper unable to begin updating

Build the project in visual studio Next time go ahead and click on prerequisite see if those Yellow warnings still show up on Prerequisite packages If that is the case select the third option Under Specify the Download location Provide UNC path of the package and try publish your project bill boyce.

Tuesday, December 7, PM. And you are right I have no problems publishing if i dont select the prerequisite options. The Prerequisites on my system, however, are not corrupted no yellow warning signs Any other ideas?

Hi, Please review this to see if it helps you out. Open a Command Prompt window and change to the directory to which you downloaded dotNetFx At the command prompt, type: dotNetFx Friday, December 10, PM.

Thanks for suggestion. This did not work for me. Wednesday, December 15, AM. Thursday, December 16, PM. Thursday, July 28, PM. Were you able to solve the problem? Monday, August 8, PM. Regards Keshav. Proposed as answer by chadnt Thursday, December 29, PM. Wednesday, November 23, PM. Thank you, Keshav. Deleting the bin and obj folders from the project folder allowed me to resolve my error identical to the screenshot above.

Thursday, December 29, PM. My 2 cents here. After uninstalling Test Track Pro the problem did go immediatelly away. Not sure why but seems like that was causing the problem. Thanks, Gabriele. Wednesday, January 25, PM. Regards, Lee Lee. Wednesday, March 14, PM. Thanks, Henry. Monday, June 18, PM.

Thanks It workd for me. Tuesday, July 17, AM. It worked! Thank you heeTop! It is finally fixed. Thanks again! Veni Vidi Giocavono X-Box. Asked 9 years, 3 months ago. Active 8 years, 11 months ago. Viewed 2k times. The error goes away if I uncheck "create setup program to install preq components" I tried copying the bootstrap packages from another machine, no luck. Add a comment. Active Oldest Votes.

I delete the prerequisite package and i've solved the problem Antonio Antonio 1, 4 4 gold badges 15 15 silver badges 33 33 bronze badges. This too solved my problem. Issue is what if that Prerequisite is needed for the program to run properly? What do you do then? In the past this worked like a charm, but something is missing or not working correctly.

This happens on a brand new VS project. In my case all was fine until I started adding code to a component. The target is. Friday, October 8, PM. Once you get this message, your done. I created a new project in VS Premium, added code, then it got the error, so I removed code until all code was removed. Still, I can NOT publish.

Windows XP Version 5. Compiling to "x86", and can't use "Any CPU". Recruitment i know this is not the issue anymore, but i don't know what happen that suddenly i don't have the Bootstrap error and now i got another error. Sunday, October 10, AM. Monday, October 11, PM. Could I get a status update?

Thanks, Kurt. Wednesday, October 13, PM. Friday, October 15, PM. Saturday, October 16, AM. At this point I would just like to know if MS can recreate and are they working on a solution. Monday, October 18, PM. Hi, Sorry for the late reply, I was out of office for a while. Regarding the specific problem you described, I still can't repro it so far. Regards, Jie Please remember to mark the replies as answers if they help and unmark them if they provide no help.

Has a solution been found to this issue - seem's I'm having it also I cannot find other that the original report on Connect - and that one is not very helpful My project is also upgraded to vs from sv and I'm on a Windows XP sp3 system. Monday, November 15, AM. Tuesday, November 30, PM. I am having exactly the same issue on Win7 32 bit. The suggestion above does NOT help. Cannot imagine Microsoft is unable to fix this!!!!! Wednesday, December 15, AM. Thursday, December 16, AM.

Is there any more information about a bug fix or workaround? Wednesday, December 22, PM. Thursday, December 23, AM. I was able to get around the problem by disabling an add-in from the Add-in manager inside VS The add-in that I disabled was from a third party called TypeMock. I was also able to make it work by turning off the option to create a setup. I suggest disabling addins and extensions in Visual Studio one by one until you find the one or ones that cause the problem.

Monday, January 10, PM. Thursday, February 3, PM. Friday, February 4, PM. Wednesday, February 9, AM. However, disabling add ins worked for me Br. Friday, February 25, AM. I published every which way possible with the same result So in desperation I decided to add some extensions into the IDE.

I added 4. Still won't publish. Den PS. Friday, February 25, PM. I take it back. I am now getting the error again. Regardless of how I configure extensions Monday, February 28, PM. Same here - but turning extensions of and on a couple of times and restarting VS in between can make the publish succesfull - you just have to have patience :-S. Tuesday, March 1, PM. I disabled all extensions one by one and this solved the problem.

Thanks for your input. Friday, March 4, PM. Tuesday, March 8, PM. Wednesday, March 9, AM. I removed unticked the requirement 'Create Setup Program to And finally it worked. Tuesday, March 22, PM. Hi Robin, I am having the exact same issue and I can see it's been kicking around since Thank you, Jonathan. Clearing the Temp folder resolved this issue for me. Monday, July 18, PM. I have tried many, but not all, of the suggestions on this trend.

At point I have decided to try Removing the Extensions one by one. So my conclusion is that it looks to be related t extensions. Sunday, January 15, PM. Fingers crossed. I am assuming at this point that there are multiple causes for this error. Some solutions work for some people, and not others. The issue arises anew, defying previous fixes that had once worked. Monday, January 16, PM. Dobson 0. Dobson; have two accounts, and forgot which one I had logged in as.

No bootstrapper issue encountered. Edited by Jonathan M. Dobson Monday, January 16, PM. Hello , I performed the procedure outlined and finally I decided the error quoted. Other than what is indicated, restarted the app vb pro.