malletKATman
Contributor
- Feb 19, 2019
- 134
I think I have figured out your logic in deriving the next FRST Search run from the previous CheckSUR.log file, and automated it in my superb text editor. Wouldn't your next search list be the following, given FRST could handle a string this long?
KB2393802;KB2534366;KB2556532;KB2644615;KB2647753;KB2676562;KB2679255;KB2709715;KB2724197;KB2799494
I feel confident enough to try this and send you the results, to cut the cycle in half. If FRST can't handle that many search elements, I'll truncate.
KB2393802;KB2534366;KB2556532;KB2644615;KB2647753;KB2676562;KB2679255;KB2709715;KB2724197;KB2799494
I feel confident enough to try this and send you the results, to cut the cycle in half. If FRST can't handle that many search elements, I'll truncate.