Issues Updating from 1703 to 1709

I believe you mentioned another Update soon, did you mean this month?

That was PCR's point.  Another upgrade will be possible shortly.  E.g. a new major version which has been in preview will be released to the public.  A related idea with what you have would be trying to obtain and use the Media Creation Tool for the version you have to get an ISO that you could use for an ISO upgrade repair procedure. 

BTW I may as well add (speculatively) one possible explanation of your errors (e.g. as shown by the UpdateAgentLCU detail) would be that you are having trouble with the servicing stack level.  Maybe that's why they aren't showing up as normal packaging problems.  In fact, saying this has just given me another idea for something to check...

OMG.  This is what you are trying to install.  I dumbly thought it was another cumulative update.

https://support.microsoft.com/en-us/help/4090914/servicing-stack-update-for-windows-10-version-1709-march-5-2018

I wonder how we are supposed to diagnose problems with this kind of update?

See if you can get a list of the updates that you have using this PowerShell pipeline.  Status is blank for me but I don't know if it would ever show anything useful.

get-hotfix | Sort InstalledOn | Select HotFixID, Status, InstalledOn

Curiously using the Sort changed the order for me.  I wasn't expecting that and that's why I am suggesting that it be listed this way.  Unfortunately the timestamp is always zero so we don't get the most accurate sort if you happen to have a bunch of updates done on the same day but it does help clarify how updates done on different days may relate.

And here is a list of what you may have for those.   Note that you can check your current build level using winver.exe.

https://support.microsoft.com/en-ca/help/4088776

HTH

Robert

Hi RA,

       Sorry Robert but I have had a really bad day and seem to have trouble taking in what you have said. 

SetupAPI.Dev.log; contains no failures and only one notation for the problem period:-  [Delete Device - SWD\PRINTENUM{910EC9C1-5874-4838-9BB9-96FB6D4C8E83}]

>>>  Section start 2018/03/15 01:21:39.354

cmd: C:\Windows\System32\spoolsv.exe

!    dvi: Access denied from Query and Remove

<<<  Section end 2018/03/15 01:21:39.384

<<<  [Exit status: SUCCESS]

I have removed Malwarebytes & SAS. 

I have removed odd unwanted software which failed to provide what I wanted

I have disconnected all attached network storage and all usb except Wacom

Update trouble shooter wants to install waiting repeat before anything else.

I am about to do a Clean Boot and then start the Update, on second thoughts maybe better tonight after a decent night's sleep.

I have not had time to DISM but SFC came up clean.

My search on UTCCatureV1 found a few references, one was to PST files (Outlook 2010 .pst files I have relocated in My Docs as I have done for 7 years) and another to a possible software conflict.  Maybe it is about time that the Log became more specific about failure events/causes

I believe you mentioned another Update soon, did you mean this month?

Just a refresher about my setup. Win10 Pro is on a 250GB SSD.  All data is on a HDD mounted in the Optical slot of my Laptop. The HDD holds all my Data Files, my Downloads and Temp files and the nominated location for Windows Virtual Memory,  all of which are on separate partitions plus a  Win 10 Pro 1703 Partition.  I have relocated the usual File Explorer links to the appropriate HDD file location (F:\ My Docs, Videos, etc and T:\ Temp plus S:\ Virtual Memory) which allows me to Dual Boot when I need to do so such as during the 1703 to 1709 problem I had.  I have used this type of setup since the start of Win XP with PCs and Laptops without problems for 16 plus years.

Will re read your post before proceeding tonight when I will hopefully be less tired.

There are 10 pages of entries:-

FWIW here is a summary of them.  There appears to be a pattern but I don't know what it would imply

15/03/2018 21:07 Event Name: WindowsNonFatalSuspectedDeadlock

15/03/2018 21:07 Event Name: WindowsNonFatalSuspectedDeadlock

15/03/2018 21:07 Event Name: WindowsNonFatalSuspectedDeadlock

15/03/2018 18:10 Event Name: WindowsNonFatalSuspectedDeadlock

15/03/2018 18:10 Event Name: WindowsNonFatalSuspectedDeadlock

15/03/2018 18:10 Event Name: WindowsNonFatalSuspectedDeadlock

15/03/2018 01:45 Event Name: CbsPackageServicingFailure2

15/03/2018 01:45 Event Name: WindowsUpdateFailure3

15/03/2018 01:45 Event Name: WindowsUpdateFailure3

15/03/2018 01:45 Event Name: WindowsUpdateFailure3

15/03/2018 01:45 Event Name: CbsPackageServicingFailure2

15/03/2018 01:45 Event Name: CbsPackageServicingFailure2

15/03/2018 01:34 Event Name: WindowsNonFatalSuspectedDeadlock

15/03/2018 01:34 Event Name: WindowsNonFatalSuspectedDeadlock

15/03/2018 01:34 Event Name: WindowsNonFatalSuspectedDeadlock

15/03/2018 01:00 Event Name: UTCCaptureV1

15/03/2018 01:00 Event Name: UTCCaptureV1

15/03/2018 00:13 Event Name: CbsPackageServicingFailure2

15/03/2018 00:13 Event Name: WindowsUpdateFailure3

15/03/2018 00:13 Event Name: WindowsUpdateFailure3

15/03/2018 00:13 Event Name: WindowsUpdateFailure3

15/03/2018 00:13 Event Name: CbsPackageServicingFailure2

15/03/2018 00:13 Event Name: CbsPackageServicingFailure2

The most common problem may or may not be related.  It doesn't seem to be concurrent enough but who knows.  You could eliminate it by temporarily disabling or uninstalling  Geolocation.   I don't know what that UTCCaptureV1 thing is either.

Otherwise the pattern I'm seeing is two sets of 

1. two CbsPackageServicingFailure2
2. three WindowsUpdateFailure3
3. then 1 more CbsPackageServicingFailure2

They each have different numbers of attachments but the last one has the most which I imagine will be a collection from all the others.  Notice that the order is reverse chronological so the top entry of each set is actually the last in the set and that is where I this final collection of attachments is.  So here is that whole thing.  Note the final path where you might find that collection.

15/03/2018 01:45              Windows Error Reporting             Fault bucket 2244041626960407138, type 5

Event Name: CbsPackageServicingFailure2

Response: Not available

Cab Id: 0

Problem signature:

P1: 10.0.16299.245

P2: Package_for_KB4090914

P3: 16299.251.1.0

P4: amd64

P5: unknown

P6: 800f081f

P7: Stage

P8: Resolved

P9: Staged

P10: UpdateAgentLCU

Attached files:

\?\C:\Windows\Logs\CBS\CBS.log

\?\C:\Windows\Logs\CBS\CbsPersist_20180315014226.log

\?\C:\Windows\Logs\CBS\CbsPersist_20180315003519.log

\?\C:\Windows\Logs\CBS\CbsPersist_20180315000913.log

\?\C:\Windows\servicing\Sessions\Sessions.xml

\?\C:\Windows\inf\setupapi.dev.log

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER26EA.tmp.WERInternalMetadata.xml

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2719.tmp.csv

\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2739.tmp.txt

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\Critical_10.0.16299.245_27ca48506c53f5b9f3d39cf383ba8db3d8c6a57_00000000_02452e3d

I don't think we have found the right stuff yet to know what is causing the failures.  Seeing  SetupAPI.Dev.log  in the collection though reminds me that sometimes there are enough clues in there about devices to try disabling or removing which do allow the update to proceed.  I don't think that your error code is normally seen in those cases but who knows.  My tack is usually changing things so the diagnostics change so I know that they are not significant to the unknown problem.

HTH

Robert

If you mean you no longer wish to be subscribed to this thread, scroll up to the top post. That's the one blueice_haller started the thread with. It's at the top of every page of this thread. Then, click the 3 dots (...) beneath his post, & select "Unsubscribe"...

Stop use My mail adress