Hi Valval__ wrote:OK, run autopatcher today. Updated admin tool w/ problem.
But checking win7 and win8 (September 15) in any combination I get permission problem and program wants to exit.
1...So, I run sweeper and it wants to delete all these files. Is this normal to have that much?
2...Already run sweeper previous month and actually deleted bunch of files.
3...Took quite a lot megabytes to download them back.
Update:
Today I got past that screen. MD5 check and all downloaded that failed yesterday.
![Smile :)](./images/smilies/icon_e_smile.gif)
1...Sweeper should only delete files that are not supposed to be there according to the rti file used to verify the release - so yes, this is normal. The month of September 2015 was very busy for 7 & 8, x64 & x86 alone, numerous deletions and numerous additions. Your broken download may be somewhat to do here. The script should have removed any PreAction deletions, but it looks like maybe it didn't get to because of a permission issue, but you did get the latest rti file. When you (or AP) ran Sweeper it used the latest rti file to verify the releases and it found all those "Extra" files - so it deleted them. This is my guess. There's only 3 ways files get removed (4 including the user), the script will remove them if listed in the PreAction section of the script, the script will also delete a partial (incomplete) download and start over with that one file, or Sweeper will remove Extra (or mismatched sized/hashed) files according to the list within the rti file.
Btw, I think there was a discussion about only updating the latest IE that each OS can run, IE11 I believe. If this is correct and you run 9 or 10, AP wont contain these updates. Again, I think, I'm not positive.
2...This is a bit interesting! If you're able to update your releases properly using AP, and they're official, Sweeper shouldn't have to delete anything - there should be no missing, extra, or mismatched files unless your download was problematic. If this happens again you may want to provide the Sweeper log so the reason can be determined. The log from the download as well. It wouldn't hurt to take a quick look at the release info (in AP) to see if any releases are unofficial, then maybe run Sweeper.exe /test /verbose to get a list (see log) of issues without deleting anything. If updating the release(s) using AP fixes nothing then the script is the problem and should be reported so it can be corrected.
The key here is that after an update you want all the releases to be official, AP's Release Info with the aid of Sweeper finding Extra files should alert you to the unofficial release.
3...I don't think you were redownloading old files, rather, the most recent updates, there were a lot of em. If there were old files in your release that were removed, they would have been corrupt files would be my guess. Possibly, files were removed because they were causing issues for some users, but after a bit of decision-making they were added back. This will happen, an update is buggy (or some other such problem) and until a fix is figured out it will be removed - then added back later. Again, so as to prevent any redundant downloading, if these kinds of things are happening it is best to provide an unedited log file for the offending release so it can be inspected.
These are my suppositions, worth about a handful of air
![Smile :)](./images/smilies/icon_e_smile.gif)