New
#311
Thanks, @simrick for rooting thru the specs and logs. The weird date 30/12/1899? She has MS Office stuff on there.... check this: What is story behind December 30, 1899 as base date?
Thanks, @simrick for rooting thru the specs and logs. The weird date 30/12/1899? She has MS Office stuff on there.... check this: What is story behind December 30, 1899 as base date?
Thanks for checking everything! I so much appreciate your help!
I will run the backup tomorrow when I have more time. That will be my homework!
Noted also to run MBAM frequently.
So what other programs should I keep and run frequently apart from MBAM and backup?
Here are the settings for defender and windows updates.
Lizzy, you're getting your updates automatically, good. Your Defender updates are current, good. MBAM will update it's definitions when you run it. Run the Defender Quick scan daily before any backup, same with MBAM. Look back a few posts where simrick suggested the Threat Scan on MBAM What extra software do I need with Windows 10 - Page 31 - Windows 10 Forums and follow those guidelines.
Don't add any more programs or delete any more programs right now. Let it all settle in. You've only been on Windows 10 for 2 weeks now and should explore the new OS for a while. Get used to it, and get comfortable with it. No wild moves..... Remember the Big Update Aug 2nd.
Enjoy your work! TC
Interesting explanation .... but that would mean that MS didn't just copy Lotus in their spreadsheet, but also applied the erroneous leap year processing elsewhere. I don't recall seeing this in Speccy reports on previous versions of Windows - did some programmer copy bad date processing for Win10?
The bug was inside the spreadsheet pgms when doing date calculations.
The Speccy shows updates to the pgms.
Date processing was always so much fun - then you had the YK2 end-of-the-world averted and you now have the micro-adjustments (only really important to mission critical applications)
But yes Oh Good Grief!
Sorry to butt in...
Actually, that's not quite how it works with the current version of MBAM.
MBAM version 2.x (currently 2.2.1.1043) [and all future versions AFAIK] will automatically check for updates as part of its pre-scan operations for a manual scan in Free, Trial and Premium version.
That change was implemented in 2014 with version 2.x, because many MBAM Free users did not know or bother to manually update before a manual scan.
That resulted in lots of help desk tickets for false positives and false negatives, because the database version that ships with the installer is always out of date by the time the setup file is run.
So, starting with version 2.x, MBAM was coded to automatically scan for updates before a manual scan.
MBAM PREMIUM, the paid version (as well as the 14-day Trial version) can also be configured to automatically update on a schedule and, if the user chooses, immediately prior to a scheduled, automated scan. (There are separate settings for this.)
But even with MBAM Premium and scheduled auto-updates, MBAM will automatically check for updates before a MANUAL scan, as long as the computer can reach the update servers.
Having said all of that, there is certainly no harm in the user manually checking for updates before a manual scan under all versions (Free, Trial and Premium).
And, as mentioned way way way way back (about 32 pages ago:)), please be aware that MBAM Free can only detect/remove malware that already made it onto the system. Realtime protection to help PREVENT infection in the first place requires a paid, Premium license.
And now I shall crawl back under my rock.:)
Cheers,
MM