Fatal Error Lnk1168:cannot open *.exe file for writing

When you use Visual Studio 2008/2010/2012 (at least I've used these versions), the link errors often occur when the compilation chain is delivered as an. exe file. What is the root cause? To tell you the truth, I don't know.

After the network search, found that there are many strange answers. My home machine configuration is lower, the speed naturally slow a lot. In contrast, the office machine is highly equipped and faster than the home. Therefore, the same procedure, the probability of the above errors is much lower in the office than in the home. If you say 10 times a day in your home, the office is only 1-2 times a day.

There are other kinds of questions on the network, you don't say I don't understand. After a few days, today in the home again when using VS2012 (home configuration WIN7 32bit,i3,2.13ghz,4 core, notebook Lenovo) and the above error occurred.

I'm really sick of the way I used to search and use on the web--though it can solve the problem, it's obviously not a good idea. I debug the program every day, the difficulty of operating hundreds of thousands of times not?

One way to find out today is:

Open the Control Panel-〉 Administrative Tools-〉 Service-〉 enable application Experience service, issue resolution.

It feels good! But even if you refer to some Microsoft forums there is no fundamental answer, even though the problem is solved. Also feel a bit depressed!

Resources:

1 http://blog.csdn.net/longteng1116/article/details/17725041

2 https://social.microsoft.com/Forums/pl-PL/3bccc355-acf4-460c-9d5a-24f12fe4d195/ Fatal-error-lnk1168-cannot-open-debugdialogexe-for-writing?forum=vcgeneral

3 http://stackoverflow.com/questions/12124146/vc-fatal-error-lnk1168-cannot-open-filename-exe-for-writing

This article is from the "Green Peak" blog, please make sure to keep this source http://zhuxianzhong.blog.51cto.com/157061/1601393

Fatal Error Lnk1168:cannot open *.exe file for writing