If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
4056892 not installing
Like the title says. Win10 pro fully updated on 1709 (OS build
16299.125) except for this patch. Win update just sits there at 0% download. I have Eset Nod32 AV and I have checked not only the compatibility list but also the AV itself and it is up to date and has been patched.. Kind of worried about hosing my system by forcing anything. My processor is a 7700k if that is important. My question is of course: Do I sit here and wait? or do I force it? Anyone else having this problem and what did you do if anything? |
Ads |
#2
|
|||
|
|||
4056892 not installing
Drew wrote:
Like the title says. Win10 pro fully updated on 1709 (OS build 16299.125) except for this patch. Win update just sits there at 0% download. I have Eset Nod32 AV and I have checked not only the compatibility list but also the AV itself and it is up to date and has been patched.. Kind of worried about hosing my system by forcing anything. My processor is a 7700k if that is important. My question is of course: Do I sit here and wait? or do I force it? Anyone else having this problem and what did you do if anything? catalog.update.microsoft.com Type "KB4056892" in and see what options are returned. If you have a 64 bit OS, then use the matching 64 bit one. The .msu you download is "defensively designed". It won't allow an install to proceed unless the prerequisites match. So in that sense, it's "relatively safe". The .msu is executable. At least on my machine, double-clicking it will kick it off. Paul |
#3
|
|||
|
|||
4056892 not installing
On 1/6/2018 4:13 PM, Paul wrote:
Drew wrote: Like the title says. Win10 pro fully updated on 1709 (OS build 16299.125) except for this patch. Win update just sits there at 0% download. I have Eset Nod32 AV and I have checked not only the compatibility list but also the AV itself and it is up to date and has been patched.. Kind of worried about hosing my system by forcing anything. My processor is a 7700k if that is important. My question is of course: Do I sit here and wait? or do I force it? Anyone else having this problem and what did you do if anything? catalog.update.microsoft.com Type "KB4056892" in and see what options are returned. If you have a 64 bit OS, then use the matching 64 bit one. The .msu you download is "defensively designed". It won't allow an install to proceed unless the prerequisites match. So in that sense, it's "relatively safe". The .msu is executable. At least on my machine, double-clicking it will kick it off. ** Paul so now the question is cumulative or delta? offers both.. |
#4
|
|||
|
|||
4056892 not installing
Drew wrote:
On 1/6/2018 4:13 PM, Paul wrote: Drew wrote: Like the title says. Win10 pro fully updated on 1709 (OS build 16299.125) except for this patch. Win update just sits there at 0% download. I have Eset Nod32 AV and I have checked not only the compatibility list but also the AV itself and it is up to date and has been patched.. Kind of worried about hosing my system by forcing anything. My processor is a 7700k if that is important. My question is of course: Do I sit here and wait? or do I force it? Anyone else having this problem and what did you do if anything? catalog.update.microsoft.com Type "KB4056892" in and see what options are returned. If you have a 64 bit OS, then use the matching 64 bit one. The .msu you download is "defensively designed". It won't allow an install to proceed unless the prerequisites match. So in that sense, it's "relatively safe". The .msu is executable. At least on my machine, double-clicking it will kick it off. Paul so now the question is cumulative or delta? offers both.. I just download cumulative ones. There's no danger of me exceeding my network cap :-) (No Netflix) Paul |
#5
|
|||
|
|||
4056892 not installing
On Sat, 6 Jan 2018 16:28:56 -0800, Drew
wrote: so now the question is cumulative or delta? offers both.. If you downloaded the delta and tried to install it it will soon tell you if it is not for you. |
#6
|
|||
|
|||
4056892 not installing
On 7/1/2018 07:37, Drew wrote:
Like the title says. Win10 pro fully updated on 1709 (OS build 16299.125) except for this patch. Win update just sits there at 0% download. I have Eset Nod32 AV and I have checked not only the compatibility list but also the AV itself and it is up to date and has been patched.. Kind of worried about hosing my system by forcing anything. My processor is a 7700k if that is important. If you go the Window$ Update route, then it should have installed fine. If you were trying the standalone installer, well... -- @~@ Remain silent! Drink, Blink, Stretch! Live long and prosper!! / v \ Simplicity is Beauty! /( _ )\ May the Force and farces be with you! ^ ^ (x86_64 Ubuntu 9.10) Linux 2.6.39.3 不借貸! 不詐騙! 不援交! 不打交! 不打劫! 不自殺! 請考慮綜援 (CSSA): http://www.swd.gov.hk/tc/index/site_...sub_addressesa |
#7
|
|||
|
|||
4056892 not installing
Drew wrote:
Anyone else having this problem and what did you do if anything? Mine had the defender update that set the magic quality flag in the registry, but WU just sat there saying I was up to date, eventually I downloaded the .msu file from the catalogue manually and it installed with no issues. |
#8
|
|||
|
|||
4056892 not installing
On 1/6/2018 5:08 PM, Paul wrote:
Drew wrote: On 1/6/2018 4:13 PM, Paul wrote: Drew wrote: Like the title says. Win10 pro fully updated on 1709 (OS build 16299.125) except for this patch. Win update just sits there at 0% download. I have Eset Nod32 AV and I have checked not only the compatibility list but also the AV itself and it is up to date and has been patched.. Kind of worried about hosing my system by forcing anything. My processor is a 7700k if that is important. My question is of course: Do I sit here and wait? or do I force it? Anyone else having this problem and what did you do if anything? catalog.update.microsoft.com Type "KB4056892" in and see what options are returned. If you have a 64 bit OS, then use the matching 64 bit one. The .msu you download is "defensively designed". It won't allow an install to proceed unless the prerequisites match. So in that sense, it's "relatively safe". The .msu is executable. At least on my machine, double-clicking it will kick it off. *** Paul so now the question is cumulative or delta? offers both.. I just download cumulative ones. There's no danger of me exceeding my network cap :-) (No Netflix) ** Paul So heeding your advice I downloaded the installer, ran it and waited. 2hrs later it still sits there looking for updates.. Would this be considered normal as it sure doesnt to me..The one good thing it made me or reminded me to do was a backup. Hopefully I will not need it although it was time to do it. |
#9
|
|||
|
|||
4056892 not installing
Drew wrote:
So heeding your advice I downloaded the installer, ran it and waited. 2hrs later it still sits there looking for updates.. Would this be considered normal as it sure doesnt to me..The one good thing it made me or reminded me to do was a backup. Hopefully I will not need it although it was time to do it. Steps: 1) Disconnect network cable (do whatever is necessary for Wifi, disable radio if that's what you're using. 2) reboot (this disables WUAUSERV, which needs to see network when you start up. When there is no network, WUAUSERV will be idle. The .msu can now work. WUAUSERV will listen to the .msu.) 3) Execute .msu 4) Reconnect network cable when convenient. And reboot for the patch to kernel, GDI or whatever, to "take". 5) Profit. Paul |
#10
|
|||
|
|||
4056892 not installing
On 1/7/2018 6:25 PM, Paul wrote:
Drew wrote: So heeding your advice I downloaded the installer, ran it and waited. 2hrs later it still sits there looking for updates.. Would this be considered normal as it sure doesnt to me..The one good thing it made me or reminded me to do was a backup. Hopefully I will not need it although it was time to do it. Steps: 1) Disconnect network cable (do whatever is necessary for Wifi, disable radio ** if that's what you're using. 2) reboot* (this disables WUAUSERV, which needs to see network when you *********** start up. When there is no network, WUAUSERV will be idle. *********** The .msu can now work. WUAUSERV will listen to the .msu.) 3) Execute .msu 4) Reconnect network cable when convenient. ** And reboot for the patch to kernel, GDI or whatever, to "take". 5) Profit. ** Paul Lessons learned...Thank you Paul! |
Thread Tools | |
Display Modes | Rate This Thread |
|
|