Mail Notification Question
-
Seem like it could be Defender that could be causing the trouble as McAfee has just updated and no trouble at all,
Wonder how many of the other members have Defender working and scanning
-
-
Well mine just broke again, that's with mail app open
I checked what was going on when it happened and defender had just done an update and was doing a scan
no errors to be seen anywhere, but mail refreshed itself when I clicked on it and started it working again
My Internet Service Provider (Comcast) provides a Free Norton Security Suite.
Norton has just updated their product and now it works much better with Windows 10.
I was recently on the Comcast forum and read about the updated Norton Security Suite version 22.5.4.24
and decided to reinstall it. I used Norton from Comcast for years with Windows 8.1 so I know the settings.
I have no Defender conflict as I am not using it.
-
So that rules out Defender
Also Norton
Also McAfee
lads we will get there in the end we wont let it beat us
-
-
So that rules out Defender
Also Norton
Also McAfee
lads we will get there in the end we wont let it beat us
I think Paul just posted that Defender updated and started a scan WHICH DISABLED HIS EMAIL NOTIFICATIONS.
He said he had to refresh his mail app to restart it. So DEFENDER can be a problem.
-
I think Paul just posted that Defender updated and started a scan WHICH DISABLED HIS EMAIL NOTIFICATIONS.
He said he had to refresh his mail app to restart it. So DEFENDER can be a problem.
Yes Sorry you are right, I for one don't like Defender tried it once and took a load of photos out it told me where corrupt but when I managed to get them up again having saved copies. ran Bit Defender and McAfee and they found them clean. so since that time have never trusted it again
-
Be funny if one of Microsoft own apps is causing the problem, how red faced are they going to look
-
just going through these now, not ran for a while
dism /online /cleanup-image /restorehealth
sfc /scannow
powershell
Get-AppXPackage -AllUsers |Where-Object {$_.InstallLocation -like "*SystemApps*"} | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
the dism has completed its restore successfully, sfc is currently running
-
just going through these now, not ran for a while
dism /online /cleanup-image /restorehealth
sfc /scannow
powershell
Get-AppXPackage -AllUsers |Where-Object {$_.InstallLocation -like "*SystemApps*"} | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
the dism has completed its restore successfully, sfc is currently running
Please keep us posted on the outcome as would love it if it was defender causing it
-
-
just going through these now, not ran for a while
dism /online /cleanup-image /restorehealth
sfc /scannow
powershell
Get-AppXPackage -AllUsers |Where-Object {$_.InstallLocation -like "*SystemApps*"} | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
the dism has completed its restore successfully, sfc is currently running
Paul I was told to run sfc /scannow first. If it is clean or repairs errors it finds there is no reason to run DISM.
DISM is only run when sfc /scannow finds problems it can't repair.
It is a step 1, step 2 process.
-
Please keep us posted on the outcome as would love it if it was defender causing it
Will do :)
Paul I was told to run sfc /scannow first. If it is clean or repairs errors it finds there is no reason to run DISM.
DISM is only run when sfc /scannow finds problems it can't repair.
It is a step 1, step 2 process.
That is how I have always done it, but I was looking at the MS forums about start menu/action centre not working and the suggestion was run things in the order I just posted
I thought it was worth a try
Quote