Windows 10: I write a critique 0f MS arrogance and you then you ask me to join the cult of "those who...

You are so clueless that you don't even know when we really don't like you.

:)

 

MS arrogant or dumb?

My sister forgot her live id. She's no geek and it happens all the time.

I backed up her photos but could not back up her contacts on her lumia 8.1 phone. There are apps but you need to sign in with the live id of course...

MS have a recovery process but her regiistered email address must have a typo as it never came. So we tried the alternative recovery. Webform asks all sorts of questions about the live id usage - emails sent, previous passwords, xbox credit card etc, assuming
that all phone users use their live id email to run their entire lives. Obviously.

But like so many real people, she never does. And why should she? MS forces you to use a live account on the phone but that doesn't mean you should drop you old email address of 10+ years.

Is MS just dumb or arrogant? They suggest recovery from a lost password is by resetting the phone, which wipes all data. If you back it up to their cloud you're fine of course - but you need that password. I think it was Windows 95 or maybe 3.1 where they
had a recovery process that needed a reboot that prevented the recovery process completing and you had to start again, then it rebooted again. Ad infinitum. It appears MS have not really learned much since then. 640k....

So, I understand MS will not allow live id to be changed without a full wipe and reset, so is there a way to export the contacts without an inaccesible app and preferably not one by one? She has over 100. Is MS determined to keep us in the 1990s?

thanks for any help

ps If anyone is thinking about preaching, please don't. It's too easy to type, but everybody knows it already and it's just arrogant. Sometimes things go wrong.

 

What is the $0F folder in FileHistory?

I just started using FileHistory in Windows 10. The first folder under the Data folder is named $0F. It is 59.2 GB. Every folder in the $0F folder seems to only have one or two entries to files saved elsewhere. These 5,922 folders are listed sequentially
with 28,284 files dated from the year 2013 to 2019.

Can I delete the $0F folder? The $0F folder is not listed as a folder to be backed.

If so, how do I prevent it from being created again?

Thanks, Rob

 

What is the $0F folder in FileHistory?

Hi Igor,

Good suggestion...

First off. DON'T DELETE THE $0F FOLDER. It appears the $0F sub-folder in FileHistory is absolutely required.

The link you sent helped me come to this conclusion. I have a BS degree in Information Systems. So, I have a good understanding (all be it primitive) of how DOS works. DOS is still the original OS system (since improved) under which all versions of Windows
still operate). I still write and use DOS based C programs that manipulate files and paths in all versions of Windows.

All that stuff (in that link you provide in your first reply) about people complaining about missing files makes sense with this explanation. Those missing files were probably in their $0F folder.

I did some comparisons as you suggested.

I'm thinking the FileHistory program caches (in RAM memory) groups of folders and files before sending them to the backup drive. When the cache space gets filled, they send the cache in one write operation to the backup drive. Then it adds the remaining files
(that were not cached from this last folder) to the next cache. Those files get tagged and written to the $0F folder (under a reference number) in the next cache write operation. There appears to be exceptions on how the FileHistory program handles some (not
all) HTML files and some URLs and some other file types. I found a lot of these in the FileHistory $0f sub-folders. And there's probably other exceptions as well because some HTML files and some URLs that were still sent to the correctly named path and folder.

I say this because the particular folder I referenced in which I found a file match, 4 files where sent to the correctly named folder in the correct path in FileHistory and the other 108 files in that same folder where written to a numbered $0F folder. The
very next folder in that same C:\ drive path had an even longer folder name and all the files lengths were the same in both folders. Thereby, the path + file names was even longer in that next folder. But all the files in that next folder were written to the
correct path and folder in FileHistory.

Maybe I'm all wet on this. But it's my best guess.

Thank you for your help. You helped me to find something that makes sense to me at least.

Rob