|
| 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
October 12th 17, 10:58 PM
posted to alt.computer.workshop,alt.comp.os.windows-10
|
|||
|
|||
My computer keeps restarting because windows update won't installKB4041676
|
| Ads |
|
#2
October 12th 17, 11:08 PM
posted to alt.computer.workshop,alt.comp.os.windows-10
|
|||
|
|||
|
My computer keeps restarting because windows update won't installKB4041676
On 2017-10-12 5:58 PM, David_B wrote:
https://answers.mi snip Do, please, comment! Nobody with a brain cares, or will click on one of your links.
|
|
#3
October 12th 17, 11:13 PM
posted to alt.computer.workshop,alt.comp.os.windows-10
|
|||
|
|||
|
My computer keeps restarting because windows update won't install KB4041676
On Thu, 12 Oct 2017 22:58:12 +0100, David_B
wrote: https://answers.microsoft.com/en-us/...3-db06fc293bfb Do, please, comment! My comment is that you've somehow posted a link to the MS Answers forum, probably in an attempt to get people to go there for nefarious purposes. That is all. (nod to M*A*S*H)
|
|
#4
October 13th 17, 02:29 AM
posted to alt.comp.os.windows-10
|
|||
|
|||
|
My computer keeps restarting because windows update won't installKB4041676
David_B wrote:
https://answers.microsoft.com/en-us/...3-db06fc293bfb Do, please, comment! Possibly that was fixed before I got it. I didn't get three updates, only one. There were no Feature Updates on my release install. Just the main Patch Tuesday update. It seems the corporate WSUS people got stung the worst. For people who "can't download the update" and are in limbo, you're "safe for today". At least nothing else can happen, until the issues caused by that (attempted) update are fixed. The WSUS people got stung because both a Delta Update and a Cumulative using the same KB number, both got installed, bricking the computers. Susan Bradley is trying hard, to get the home users to follow the standard recipe (delete SoftwareDistribution), but at this point, I can't even tell if the damn update got past that point or not. If it is rolled back, you'd want to then reboot the machine before it can make another attempt to install. So that means "timing is everything" when working on it. I can't expect home users to figure out some of this stuff, if this is the first time they've been "screwed by WU". I think Home Users can recover from the (non-WSUS) version of the problem. Perhaps pulling the network cable, before the reboot (and it backs out the attempted update), will give a period of calm to delete SoftwareDistribution contents ? If it had tipped over my machine, I would already have had a chance to deal with it. But since the Patch Tuesday one came in OK, I don't have the materials to work with, to see if timing the repair right will work. If you leave the network cable connected, it's only going to install the same (stale) update again and again. There are other threads, describing using DISM to try to fix it. In the first example, it looks like someone running the current release (15063). And you can see a reference to '608 and '674 (current). ******* output of DISM /get-packages ******* Package_for_rollupFix_Wrapper~31bf3856ad364e35~amd 64~~15063.674.1.8 Has a state of pending and no install time Package_for_rollupFix_~31bf3856ad364e35~amd64~~150 63.674.1.8 has a state of pending install and an install time of 2:49 Package_for_rollupFix_~31bf3856ad364e35~amd64~~150 63.608.1.23 has a state of pending install and an install time of 2:50 ******* example of someone rolling back their 14393 updates ******* Apparently the drive letter can vary, so it may claim to be on D: or F: or ... Dism /image:C:\ /get-packages /format:table results.txt Dism /Image:C:\ /Remove-Package /PackageName  ackage_for_Rollupfix_wrapper~31bf3856 ad364e35~amd64~14393.1770.1.6Dism /Image:C:\ /Remove-Package /PackageName ackage_for_Rollupfix~31bf3856ad364e35 ~amd64~14393.1770.1.6Dism /Image:C:\ /Remove-Package /PackageName ackage_for_Rollupfix~31bf3856ad364e35 ~amd64~14393.1715.1.10And if you cannot boot a machine, if you use your Emergency Boot CD or your Win10 15063 Installer DVD, you can probably get to a Command Prompt. Many of the commands accept offline syntax, to work on an image. However, I wouldn't expect /Remove-Package to work offline, and that's likely to only work while a system is running. If you cannot boot of course... you're screwed. Same goes for any kind of Repair Install, which requires a booted system. Very messy. ******* https://support.microsoft.com/en-us/...date-kb4041676 "Windows devices may fail to boot after installing October 10 version of KB 4041676 or 4041691 that contained a publishing issue" And yet KB4041676 only contains one file on the catalog server, so I fail to see why those three packages above show up. Imagine what would happen if users had control over updates ? :-\ Paul
|
|
#5
October 13th 17, 09:23 AM
posted to alt.comp.os.windows-10,alt.computer.workshop
|
|||
|
|||
|
My computer keeps restarting because windows update won't installKB4041676
On 13-Oct-17 2:29 AM, Paul wrote:
David_B wrote: https://answers.microsoft.com/en-us/...3-db06fc293bfb Do, please, comment! Possibly that was fixed before I got it. I didn't get three updates, only one. There were no Feature Updates on my release install. Just the main Patch Tuesday update. It seems the corporate WSUS people got stung the worst. For people who "can't download the update" and are in limbo, you're "safe for today". At least nothing else can happen, until the issues caused by that (attempted) update are fixed. The WSUS people got stung because both a Delta Update and a Cumulative using the same KB number, both got installed, bricking the computers. Susan Bradley is trying hard, to get the home users to follow the standard recipe (delete SoftwareDistribution), but at this point, I can't even tell if the damn update got past that point or not. If it is rolled back, you'd want to then reboot the machine before it can make another attempt to install. So that means "timing is everything" when working on it. I can't expect home users to figure out some of this stuff, if this is the first time they've been "screwed by WU". I think Home Users can recover from the (non-WSUS) version of the problem. Perhaps pulling the network cable, before the reboot (and it backs out the attempted update), will give a period of calm to delete SoftwareDistribution contents ? If it had tipped over my machine, I would already have had a chance to deal with it. But since the Patch Tuesday one came in OK, I don't have the materials to work with, to see if timing the repair right will work. If you leave the network cable connected, it's only going to install the same (stale) update again and again. There are other threads, describing using DISM to try to fix it. In the first example, it looks like someone running the current release (15063). And you can see a reference to '608 and '674 (current). ******* output of DISM /get-packages ******* Package_for_rollupFix_Wrapper~31bf3856ad364e35~amd 64~~15063.674.1.8 Has a state of pending and no install time Package_for_rollupFix_~31bf3856ad364e35~amd64~~150 63.674.1.8 has a state of pending install and an install time of 2:49 Package_for_rollupFix_~31bf3856ad364e35~amd64~~150 63.608.1.23 has a state of pending install and an install time of 2:50 ******* example of someone rolling back their 14393 updates ******* Apparently the drive letter can vary, so it may claim to be on D: or F: or ... Dism /image:C:\ /get-packages /format:table results.txt Dism /Image:C:\ /Remove-Package /PackageName ackage_for_Rollupfix_wrapper~31bf3856 ad364e35~amd64~14393.1770.1.6 Dism /Image:C:\ /Remove-Package /PackageName ackage_for_Rollupfix~31bf3856ad364e35 ~amd64~14393.1770.1.6Dism /Image:C:\ /Remove-Package /PackageName ackage_for_Rollupfix~31bf3856ad364e35 ~amd64~14393.1715.1.10And if you cannot boot a machine, if you use your Emergency Boot CD or your Win10 15063 Installer DVD, you can probably get to a Command Prompt. Many of the commands accept offline syntax, to work on an image. However, I wouldn't expect /Remove-Package to work offline, and that's likely to only work while a system is running. If you cannot boot of course... you're screwed. Same goes for any kind of Repair Install, which requires a booted system. Very messy. ******* https://support.microsoft.com/en-us/...date-kb4041676 Â*Â* "Windows devices may fail to boot after installing Â*Â*Â* October 10 version of KB 4041676 or 4041691 that Â*Â*Â* contained a publishing issue" And yet KB4041676 only contains one file on the catalog server, so I fail to see why those three packages above show up. Imagine what would happen if users had control over updates ? :-\ Â*Â* Paul Many thanks, Paul. :-) I learn much from you! I suspect that other folk reading the groups will also gain from reading your response. -- David B.
|
|
#6
October 14th 17, 12:35 AM
posted to alt.computer.workshop,alt.comp.os.windows-10
|
|||
|
|||
|
My computer keeps restarting because windows update won't installKB4041676
On 12-Oct-17 11:13 PM, Char Jackson wrote:
On Thu, 12 Oct 2017 22:58:12 +0100, David_B wrote: https://answers.microsoft.com/en-us/...3-db06fc293bfb Do, please, comment! My comment is that you've somehow posted a link to the MS Answers forum, probably in an attempt to get people to go there for nefarious purposes. That is all. (nod to M*A*S*H) It drew out the fact that RonNNN was/is lurking here! ;-) -- David B.
|
|
#7
October 31st 17, 04:36 AM
posted to alt.computer.workshop,alt.comp.os.windows-10
|
|||
|
|||
|
My computer keeps restarting because windows update won't installKB4041676
David_B wrote:
https://answers.microsoft.com/en-us/...3-db06fc293bfb Do, please, comment! 1. Problem #1,2 and 3: Win10. 2. Who gives a sh*t about that KB? 3. TURN OFF ALL UPDATES and your problems will dissappear.
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Linear Mode
