Specifically, I can confirm that the engine was updated on my main Win7, internet-facing, machine as part of the usual daily updates recently and I can confirm (by experiment) that the engine is updated in both Win7 (MSE) and Win10 (Defender) off-line machines if the “recent definitions” file mpam-fe.exe is downloaded from the MS site, transferred to the off-line machines via USB drive, and installed there.
I cannot explain the contrary statement, unless it only refers to on-line Win10 Defender? I emphasise that my two off-line machines did get the new engine, apparently (merely) by running the current mpam-fe.exe file. To summarise: I didn’t take any special steps to get the new improved engine (5.2) but I did, successfully, find that it had arrived both on-line (on my main machine) and off-line (using file mpam-fe.exe to transfer to two off-line machines, one Win7 MSE, one Win10 Defender).
Win7 Pro, MSE.Īll I can say is that a) I have Windows Update set to “never check” and I install updates by a scheme using your AKB2000003 “Group B” listings (my thanks again to you and MVPs) - so a new engine version shouldn’t get on to my machine via WU b) I usually update MSE on my main machine by manual update once or twice per day (to get thinking time, or to go for coffee) c) I suspect that delivery of a new engine version coincides with a change of the 2nd field of the definitions version (currently 259, was 257 before yesterday) - I keep a log of definition numbers but not of engine versions d) I imagine that a significant change in the engine might have to be synchronised with a corresponding reset of the definitions data or vice versa.
0 kommentar(er)
