save not doing anything
I have a csharp file open in the editor.
I make a change.
I see the filename in the title is "modulestartup.cs*"
The * at the end denotes that the editor knows the file has changes.
Click on "save" in menu, or press ctrl + s
Nothing happens.
Closing the file - the editor prompts to save changes. Say yes.
File is closed. Open the file again - changes have been lost.
This doesnt happen everytime I am not sure how best to replicate.
Add Comment
Not sure if this is related but I has an instance of VS2015 open at the same time. After closing vs2015 and restarting visual studio 2017 the problem seems to have gone away.
Hi Darrell, did you work with any source control tool when this issue occurred?
I have this exact same problem, happend as of this latest VS update. I click save over and over, nothing happens. I then close the file, it asks me if I want to save, I click yes. I then re-open the file and my changes are gone.
Hi Kris, did you work with any source control tool when this issue occurred?
Thank you for your feedback! Was not able to repro this, does this happen with any particular kind of project ?
We look forward to hearing from you!
I have this same issue. After searching online I found many people have reported this issue, but Microsoft keep asking for more information or even close tickets due to not enough info.
Unfortunately there is no more info to give. There are no error message, no obvious issues, it simply just doesn't save. I tried clicking save, save all, CRTL + S and none work. When if you close the file, it asks if you want to save before closing, I click "Yes" and it closes without saving.
I didn't have this issue until I upgraded from VS2015 to VS2017.
However I do find that if you wait a few minutes, it randomly starts to work again (though not all the time). It is totally random when it happens. It just happened to me moments ago and I've been working on and saving my work for the past 5 hours, yet it randomly decided to stop saving now (it has started working again).
The only thing I can think is its silently getting an "access denied" issue. Though I don't see why as I'm an admin, and I'm running visual studio as an administrator.
I do hope Microsoft look into this issue, instead of just closing it like many others I found.
Hi Ben,
Did you work with any source control tool when this issue occurred?
We are trying to figure out what is the root cause.
Thank you for helping us build a better Visual Studio!
Hi, Sorry for the late response.
I'm using TFS for source control.
I haven't noticed this issue happening for me for a few weeks now. Perhaps it got resolved in an update, but I agree with Ben -- there's no clear indication of when/how it happens. And it does not seem to be project-type specific. It happens when working in C# files and Typescript files for me.
Save issue. Approximately after every 15 minutes of use, none of the following works on files changed:- Save File, - Save All Files- Trigger save question by closing solution.In last case Visual Studio in no way signals that save was unsuccesfull but nothing is saved. When you reopen file, changes are gone. Co-worker has some issue continuously. Both running on Windows 10 Creators.There are no file permission issues. It might be however that parts of visual studio are running as administrator nowadays (we have seen more problems in that area) and temporarily lock files.Problem seems to have been introduced month ago in .5.3 release.When you feel in a good mood and continu editing and compiling, often after 5 more minutes save works again. Weird is that the compiler sometimes picks up the unsaved changes and sometimes not.Especially with large solutions (20+ projects) this costs considerable amount of time. After some time, you get used that Visual Studio 2017 is not reliable with your changes anymore, but you can copy & paste to Notepad evreything that has a * changed indicator, restart VS and paste everything back (of course disable autoformat).Weird problem and even more weird it is not getting attention; when we would ship it like this, the phone would be ringing constantly and we would loose 25% in installed base in a few months. But there is no real alternative for Visual Studio on Windows, so live with it till solved.
Entered case information over 300 words to aid. But obviously save in the developer community is not reliable. Have no reproduction, but occurs every 15 minutes approximately since .5.3.
Forget last comment. It seems that the Developer COmmunity has some caching issue when adding comments.
So, the issue could not be reproduced, right?
So, the issue could not be reproduced, right?
Issue can be reproduced but worked around when occurs. Did not know how to provide a workaround when entering it on the phone.
Could you please reproduce it without any source control tools?
Thank you for your feedback! Unfortunately, right now we don't have enough information to investigate this issue and find a solution. If this is still an issue for you, please update to our latest version. If you are still able to repro it, please provide us with more info! Thank you for helping us build a better Visual Studio!
Instead of closing a ticket because of "Not enough info" when we've all given you as much information as we have. Why don't you tell us how we can get you more info? For example, are there any log files for Visual Studio that could be recording errors when the save button is clicked?, If yes, where are they?
Hi Ben, sorry for the miscommunication from our part. I think we should have been more diligent here. Having said that, can you please try out the steps mentioned by Elvin in other comments in case you face the issue again (assuming the issue repros for some time after it is encountered at least once).
Steps:
1. If the saving issue occurs, click "Send Feedback>>Report a Problem".
2. On the opened feedback page, click "Report new problem".
3. During the step "Attachments", use "Record" function and perform the saving issue for several times and stop record. Then wait the data collecting finish.
4.Close everything (no need to submit a new ticket) and open folder
%AppData%\Local\Temp\Microsoft\VSFeedbackCollector\VSFeedback_Collector_0 (maybe 1, 2 or 3, based on the number of record times. Please make sure open the latest one).
5.Upload the Dump file and the ETL trace file.
6.Upload the Activity Log file under %appdata%/Microsoft/VisualStudio/<VS_Instance>/ActivityLog.xml
The files that might be generated due to the steps might be very large. As such this step might require quite a lot of time to complete and might sometimes give the impression that the entire system is hung. I would wait several minutes to let it complete on its own. Please let us know if you need more help in getting these logs for us. Sorry for the inconvenience and thank you so much for your patience.
Solution by
Add Comment
This ticket should no longer be tagged as needs more info. I think it should be investigated with high priority.
While the problem occurrence is annoying difficult to corner because of its sporadic occurrence, Ali's described workaround has been exercised at my organization with scores of reports of the save file problem occurring via the VS 2017 UI. All so far have reported invoking Ali's extension to save the file subsequently works. Given the severe data-integrity nature of this Microsoft Visual Studio 2017 bug, it'd be tremendously disappointing if Microsoft does not now thoughtfully use this lead to fix the problem.
Considerations for Microsoft:
1) Why does executing the code above apparently succeed in stopping threads that block many Visual Studio 2017 operations including save file?
2) Bearing in mind 1), what threads are candidates for prospectively "spinning out of control" and preventing Visual Studio UI save file interaction?
3) In what way or ways is the dte2.Properties("TextEditor", "AllLanguages").Item("ShowLineNumbers").Value assignment from an extension written in VB different than the analogous operation from the Visual Studio UI (that unlike the VB extension is prone to being somehow blocked)? Note that doing this operation via VB has been 100% effective in removing the blockage, whereas via the UI it sometimes helps and sometimes doesn't.
Solution by
Add Comment
Voting up this solution.
To be clear, the "latest 15.7" build Aditya was referring to was 15.7.3. A number of people in my organization have evaluated 15.7.3 (and 15.7.4) and indeed none of us has seen these severe save problem come up again.
The 15.6.3->15.7.3 update additionally was observed to fix a similarly sporadic problem with VS2017 searching which may have had the same root cause.
Just curiosity: did my colleague Ali's comment clue MS development in on "one of the root causes" Aditya?
I hope MS didn't sit on information about the looming potential bug fix while simultaneously tapping its client-base to perform extremely time-expensive requests for perfview "silver-platter" type bug reports. This of course would be highly discourteous.
Hi Craig,
Thanks for letting us know that the issue is not being seen on your end after the update. The save workflow in Visual Studio is quite complex and has quite a few components taking part in it from Language Services to the Editor to third party extensions. Any of these components can cause save to fail due to a bug in them. The root cause we identified was due to Team Foundation source control component. We only released the solution until we were reasonably sure there weren't any other major causes for the failure as there can be other failure points too.
We will make sure we communicate more clearly and transparently about potential causes but sometimes its hard to associate a cause to problem when the bug is very elusive and intermittent. Having said that, we are still looking out for other causes if any that might interfere with the workflow. Also to make sure each cause get its due attention from the appropriate component owner, we encourage customers to log separate bugs with traces that can identify each of the root causes separately so that it doesn't get lost in comments.
Thanks for the all patience and helping us find and fix issues in Visual Studio. We hope the update fixes the issue for good. Let us know if you do see the issue again and we will take a look at it as well.
Solution by
Add Comment
My proposed solution doesn't work always, but seem unable to remove.