Cumulative Update KB4016250 for Windows 10 v1703 Build 15063.11 Insider
-
Have not had any problems updating Windows Defender on the Insider version....Build 15063.11
It is the Creator Preview which is having problems.....Build 15063.11
Same build different drivers and setup.?
-
-
Have not had any problems updating Windows Defender on the Insider version....Build 15063.11
It is the Creator Preview which is having problems.....Build 15063.11
Same build different drivers and setup.?
I had this issue too. I'm working in a VirtualBox VM so I restored back to the pre-update snapshot and applied the CU again. This time it seems to be clean. Ho Hum!
-
- I am still getting this failed update message for Defender:
- these are the current definition details from Defender
- am I up to date or what?
- the original update Error keeps coming back..!!
-
- I am still getting this failed update message for Defender:
- these are the current definition details from Defender
- am I up to date or what?
- the original update Error keeps coming back..!!
After an update this morning:
Try the fix from Vincent's post, worked for me:
Delete following registry key:
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MpSigStub
Restart computer.
Run update again.
-
-
- that did it..
- thanks, Mike..
-
I found the update waiting when I shut down last night, it completed successfully when I turned on just now.
Everything seems hunky dory.
-
It seems to have fixed by itself or by Windows Updates.
I have tried it this morning and nothing, now it is installed.
-
Depends on which version installed....Creator Preview will not allow updating Windows Defender unless you delete mpsigstub in the directory.
A clean install Build 1703 from an ISO will allow even though they have the same winver, as it is based on Insider, which is a more advanced O/S.
Last edited by dencal; 02 Apr 2017 at 15:27.
-
Don't understand, worked once but still a problem. I'd like to compare some notes. I think it went like this: At the time I got a notice that 15063.11 was available, notice that there was an WD definition update was already there in the list above 15063.11 notice but this update installed first and only than WD update refused to work. It may be that WD update was meant for 16063.0 and people that installed it earlier don't have such a problem.
I would also like to know if ones having problem with WD update also have a problem with sfc /scannow ? It may be some connection there.
No problems with .11 or with WU. Scannow just completed with no errors. If you have the iso 15063 might suggest a repair reinstall (run it like you were upgrading) from the iso, and see if that will straighten it out...
-
-
Depends on which version installed....Creator Preview will not allow updating Windows Defender unless you delete mpsigstub in the directory.
A clean install Build 1705 from an ISO will allow even though they have the same winver, as it is based on Insider, which is a more advanced O/S.
I am running 15063.11, last clean install 15060, upgraded through 10561 to 15063.0 and now as said .11 yet I have no issues updating Defender definitions with MpSigStub present. I have never removed nor edited it: