Lucky for me, all the work I had done on the deleted spacestation rooms mod has already been uploaded to steam before Disaster struck. Unfortunately, all the new work which included new tiles, new room designs plus some fixes I did for other mods not mine have been totally and irrevocably lost due to Microsoft's stupidity and will take me about 2 weeks to redo. The only reason I'm putting this up here is because you may not even know it, but you most likely are running a different windows 10 Pro build.
If you are using Windows 10 Pro, you might want to check to see if your running build 1703. If you are, and depend on programs like file history restore, or any of Microsoft's backup and restore programs, if your build is 1703, you need to check your backup locations. When I say check, don't depend on the list that shows up using file history restore. Look in the file history section your saving data in. The directory's name is FileHistory. The best way to know if your effected, is just do a properties check on that folder. If it says something like 1.0 to 2.0 mb, you will now know that unless you have copies stored somewhere, all data backed up with that program has been officially lost. Looking into the folders you will see just about every file name with the data showing 0 for each item. It's also happening with restore points as well. Only part that seems to work with no issues is backing up using file image.
I do a lot of testing, and a lot of times it causes my operating system to get corrupted so I just restore using many of the features above. It just so happened, I was getting BSOD so formatted the boot drive plus one of my game drives and when I went to restore from backups, I didn't even get an error message. Starbound server crashed with a ton of errors, and my Apachiserver would not load up telling me the MySQL files were missing. It was then I looked into the sections where they were saved, and discovered everything at 0. I had to look back on another drive that luckily was a removable and not effected to get back data that was almost a month old. When I went onto Microsoft's website to see if similar issues was getting reported, it was then I discovered not only a lot more people reporting this, but Microsoft basically replying with macroed messages that had nothing to do with what is getting reported in the first place. What it comes down to, is they know about this, but are doing nothing about it because they don't want to say they screwed up. What I also found out was that this is happening with build 1703. I at first thought ok, I didn't upgrade to 1703, something else must be causing this. But then I found out Microsoft pushed an update in a way, many had no clue they were getting. When you get an update, or about to get one, your update program tells you and gives you an option whether you want to get it or not. Turns out, this was pushed in a way just about everyone was not told a thing about it. And worse, the normal windows.old that is your old backup of windows in case something goes wrong, was never done. Microsoft wants everyone upgraded. Whether we like it or not. Heck, I had to do a lot of registry changing to stop microsofts servers from upgrading my system back to 1703. I also noticed all my older versions made with the upgrade tool were all upgraded to 1703. Again, if it was not for the fact I have removable hard drives, and dvds, Id be in a lot of trouble. Microsoft has even taken the older versions off their servers.
If you haven't lost any important data, and see your backups are like mine, all at 0mb, either use another program to back them up or just copy paste into another folder and either burn them to a dvd or a removable hard drive. If a lot of you reply and want to know what I did to stop Microsoft from forcing me back to 1703, let me know. I'll write a tutorial.
A lot of work was lost. This didn't just effect new backups, it effected ones done a year ago. Only thing that saved me was having a duplicate copy elsewhere. Also, not sure why, but a lot of steams games that save to one drive are 0mb as well. The error logs for the system itself are packed with errors, and these are caused by the OS itself.
I did a fresh install of windows on 3 separate machines with nothing else installed. File history started failing immediately after the pcs updated to 1703. Two machines couldn't revert back to previous build as there was no windows.old made to restore them and drive space is/was not an issue. The one machine that I was able to roll back, and again this was a test with nothing else installed, became corrupted where the account would not fully load in and then despite being told the update had issues, the system still shortly after upgraded to 1703 with even more issues.
So again, if your having the same issues and want to stop your system from being forced into 1703, let me know, I'll post on what I did to my machine and my family's. Just don't go formatting your machines until your 100% positive you have backups that are really there. LOOK INTO THE FOLDERS for verification, not what the programs display to you.