Windows 10: 200,000+ files added in only 2 days?

Microsoft Defender said I had 700,000+ files when I scanned my computer two days ago. I scanned it again today, and it's saying I have around 900,000 files. Anyone know how I could've ended up with 200,000 more files even though I barely saved anything new, and I deleted a bunch of files for games and other apps that I didn't use? And Defender said that no threats were found, so I'm even more confused.

:)

 

User.000 issue after updating to 1909

I'm one of the many people suffering from issues with user profiles after applying Update 1909 to Windows 10. I've read all the threads I can find on the topic here and have followed the suggestions, all to no avail. Any other thoughts are appreciated.

After applying Update 1909, the ProfileImagePath was changed to c:\users\User.000
One file that was always in use and couldn't be removed was left in c:\users\User (can't recall or find the exact file now), so I could never rename or remove the c:\user\User directory.

I followed the multiple suggestions from Brink and others:

• Rebooted at least 6 times
• Enabled hidden Administrator
• Booted into Safe Mode
• Changed ProfileImagePath
• Tried to rename c:\users\User but couldn't because a file was still in use
• Copied all data from c:\users\User.000 into c:\users\User
• Rebooted and had temporary profile
• Followed steps in Brink tutorial to change ImageProfilePath; rebooted with no change
• Restored using Restore Point from before Update 1909 - returned to single profile state (User.000)
• Removed each update that was installed individually and rebooted after each update removal - profile state never changed
• After all updates were removed, repeated the steps above with hidden Administrator, changing profile, etc. - same issue with file in use in c:\users\User
• Followed all steps above with hidden Administrator but without copying files from User.000 to User - same results

Any suggestions are greatly appreciated!

 

File History Error 200 Every 2 Days?

nixed: I've made some suggestions on your error 200 problem at the end
I think my own FH problem is now solved thanks to clues posted here - So thanks guys
----

Unlike you, I wanted to abandon all old backup data and restart from scratch, but FH kept failing to initiate (post #20)
After reading Steve C's posts #16 & #18 carefully, FH now seems to be OK for me.
I went a bit further than Steve recommended
I deleted both of the 2 subfolders (Configuration and Data) from %LocalAppData%\Microsoft\Windows\FileHistory

1. Stopped FH in Control Panel
2. Checked FHSVC was actually stopped (Task Mgr/Services)
3. Deleted both Configuration and Data from %localAppData%\Microsoft\Windows\FileHistory
   leaving FileHistory empty
4. I also cleared the File History event log, just to give me a clean sheet
5. Re-booted while FH was switched OFF

After restart, I also deleted FileHistory folder from my external backup drive
(You probably won't want to do this )

In Control Panel, I turned FH back on. I think I had to click Run Now to kick it off. and all was well!! *Biggrin
-----


nixed Here are my guesses at solving your problem


Looking first in the backup drive, the Data folder contains all the actual file backups
and the Configuration folder is small holding Config1 & 2 and Catalog1 and 2

The %LOCALAPPDATA% Configuration folder holds Config1 & 2, Catalog.EDB 1 & 2 and Catalog.JFM1 & 2
- similar to but not direct copies of the Backup equivalent.

I think the local Data folder (called the staging area) must be the local data cache for when the backup drive is offline

Guess 1
The local Data staging area folder is not critical and is created at run time

Guess 2
Your error 200 may be caused by incompatibility between the two sets of Config and Catalog files
I guess the versions on the backup drive are the more important
If you delete the APPDATA versions first, there can't be a conflict.
- but the backup versions could be corrupted somehow.

Conclusion.
You've got nothing to lose.
Do steps 1 to 3 and 5 as I did above (maybe not step 4)

Explore the top folders in your backup drive, just so you know what they look like
e.g. note folder names & paths to the Config files

OR, if you want to, Delete the backup FileHistory folder (Nuclear option)

Then restart FH. If it finds existing backup data, accept and continue.

If FH restarts successfully, I suggest you again explore the backup folders as above and update your record

Good luck

 

File History Error 200 Every 2 Days?

Ah yes I've had to do that to get it to restart over completely. FH is great when it works, what causes this issue is not known. It says error with the configuration file but it doesn't seem to be reliably set off. Updates naturally can cause it to happen and have for me but it seems to happen randomly. Always good to make a restore point and backup of windows before updating.