I’m experiencing problems with saving my file now which is super frustrating as a lot of work is being wasted.
I can’t copy objects to another rhino file either.
I hope in the future that the serialization of the 3dm table can be done eventually skipping bad objects instead of stopping the entire save!
Ideally I can also be pointed towards the objects causing the error.
Edit: Tried selbadobjects and got rid of a few. Didn’t help.
Hi Mathias -
The best way (the only way) to make this better is by supplying 3dm files that we can use to reproduce an issue. You can upload private files from Rhino Accounts.
-wim
Edit: I had two difference warnings depending if I save on network drive or locally.
Turned out that the issue was my C: was full. 
Would be nice to write in popups in the future!
Side note - i had issuing objects previously that couldnt be saved making it impossible to save the file but that issue was due to a conflicting plugin. My fix back then was to serialize objects in grasshopper containers and opening in another rhino instance (cumbersome for many objects)
Hi Mathias -
Thanks. We have that request on the list as RH-11002 Error writing file
-wim
Cheers - might add also specify whether the disk issue is that target disk (network drive) or locally for temp file.
Another thing: I’m in a 300mb rhino file. I managed to get 2gb free on my C drive.
When saving, rhino quickly drains the harddrive to 0mb free and I get the same error.
Temp and autosave files usually are in AppData
C:\Users\user\AppData\Local\McNeel\Rhinoceros
Nothing saves like knowing where AutoSave is haha
Freeing up 2GB on your C drive is not even close to enough for your system in general to be working properly, and an SSD that close to full is not going to work well. You need more storage space a year ago.
The temp files when saving on a network drive ended up in c:\users\username\appdata\temp\RHI2323.tmp (Not Mcneel folder)
My tmp file ended up being 28gb. I was confused untill I found out that I had done a pretty sick mesh|plane intersection that left me with many many lines, causing it to save forever and taking up space.
If saving directly on local drive it seems that the temp file is in the target folder.
Edit: @wim i managed to find the source of why my curves were so heavy.
They were baked directly from grasshopper but somehow got their own serialization baked as a user attributes. This is definately a newly introduced bug in grasshopper:
I’ve created another thread for that bug here : Bug - Baking includes serialization text as userstring
