Windows 10: Windows update failing - version 1709 Update - no real error message.

Hi all, I am having a frustrating issue at the moment, where my pc is taking 20 minutes to boot - this is primarily because it keeps trying to install several windows updates, gets to 30% after multiple restarts, then fails, and says "recovering original windows installation" and finally boots up. It then presents a list of failed updates. This is below.


These all see to be for Windows version 1709. Can anyone tell me if my issue is possibly because, acording to my system I have version 1703 - and if so, how do I get it to 1709 so i can install these and move on?




Any advice please? This is driving me nuts. The only thing I have found online is recommendations of a full re-install, which i dont want to do, not with hundreds of Gb of games, and all the setup for HOTAS, Oculus and everything to do again, that will always be last resort for me.

I have tried:

• Uninstalling BitDefender and trying again.
• DISM /Online /Cleanup-Image /RestoreHealth.
• Using the Windows Upgrade Assistant.
• Running updates in Safe Mode.

Everything I have tried has the same result. Any help would be appreciated, as a re-install would take me a couple of days to get everything back to where it is now. Other than these updates the system is perfectly stable and runs well.

:)

 

feature update to windows 10 version 1709

Hello Everyone

i update my windows 10 regularly but form this update "feature update to windows 10 version 1709" my laptop is not updated.

in my laptop "feature update to windows 10 version 1709" this update is failed almost 35 times windows downloads update properly but while installing this update it goes to the 95% but after some time it will show the error message to can't update it right
now like this and it will show me the error message like this "Error 0x80244018".

Please tell me the solution for this update.

 

Problem with Windows 10 Version 1709 for x64-based Systems update (KB4088776)

When trying to perform a windows 10 update, the update failed and an error message was received :

2018-03 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4088776) - Error 0x800706be

What has to be done to load this update ?

 

1) Find a flash drive that you can format ( > or = 8 GB)
2) Create a bootable Windows 10 iso:
Download Windows 10
3) Uninstall all AV software (always on and manual)
4) Place the computer in clean boot:
https://support.microsoft.com/en-us/...oot-in-windows
How to perform a Clean Boot in Windows 10 - TechNet Articles - United States (English) - TechNet Wiki

5) remove nonessential hardware
docks
USB devices
printers
headset
speakers
bluetoot devices
USB drives (other than a windows 10 iso if used for the upgrade)
USB Wireless Mouse or Keyboard Receiver, USB Wireless Network Card,


6) ) These should be the only attached devices:
wired mouse
wired keyboard
monitor

7) Check the drive to make sure that there is > 25 GB free space
8) Post an image of disk management into the thread:
Disk Management - How to Post a Screenshot of General Tips Tutorials

9) Open administrative command prompt and type or copy and paste:
10) sfc /scannow
11) dism /online /cleanup-image /restorehealth
12) chkdsk /scan
13) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

14) Remove all unused SATA devices (only have one drive available during the windows upgrade)
15) Uninstall non-Microsoft disk encryption software
16) Run disk cleanup to clean temporary and system files

17) disconnect wireless using hardware off if available
18) disconnect Ethernet or cat5e cable
19) Insert the bootable windows 10 iso into any USB port
20) Open file explorer > identify the bootable windows 10 iso flash drive > click on it and launch setup or setup.exe
21) perform an in place upgrade repair using the text and images in this link:
Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials
22) With a successful upgrade you can then reconnect the internet and perform updates.

If the above works then you are set.
If the above fails then look for a windows error message and code. A failed windows upgrade creates Panther logs and these can be troubleshooted if necessary.

 

Do you use any oc tuner for either your GPU or CPU like AI Suite if you have a Asus MB do you use an internal sound-card or the on-board same question with your GPU do you use a Graphics Card or on-board GPU, final thing check your c:\ for space looks like you do not have enough storage so right click c:\ select properties run a cleanup only not the system cleanup
If it still fails, i am out of ideas except i have read that some nvidia driver will prevent the install of 1709 same goes for sound card my SB Zx was preventing upgrading to new build on my test pc.

 

This update is actually 1709 trying (and failing) to install. Follow zbook's advice in full for the best chance of success.

 

Ok thanks everyone, I will try this over the next couple of days around work. It looks like a long process so I will run it through carefully and then report back.

To respond to Kimkl, nothing I am aware of is overclocked, I have 90Gb space on my c:\. I have a Gigabyte mb, I use onboard sound, and I use an Nvidia 1080 GPU.

I will try to report back in a couple of days at least, I am nt sure I have a wired keyboard, so may need to go out and get one. Thanks for the advice everyone.

 

Here is my Disk Management picture as per the instructions.




Results of the CMD Prompt instructions.

Microsoft Windows [Version 10.0.15063]
(c) 2017 Microsoft Corporation. All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>dism /online /cleanup-image /restorehealth

Deployment Image Servicing and Management tool
Version: 10.0.15063.0

Image Version: 10.0.15063.0

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\Windows\system32>chkdsk /scan
The type of the file system is NTFS.
Volume label is Windows.

Stage 1: Examining basic file system structure ...
457984 file records processed.
File verification completed.
11418 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
574824 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
58421 data files processed.
CHKDSK is verifying Usn Journal...
37921680 USN bytes processed.
Usn Journal verification completed.

Windows has scanned the file system and found no problems.
No further action is required.

243567615 KB total disk space.
150312708 KB in 263851 files.
173764 KB in 58422 indexes.
0 KB in bad sectors.
574471 KB in use by the system.
65536 KB occupied by the log file.
92506672 KB available on disk.

4096 bytes in each allocation unit.
60891903 total allocation units on disk.
23126668 allocation units available on disk.

C:\Windows\system32>

 

Ok guys, managed to get the time to run through the whole process today. It failed on the repair. Effectively after the first reboot, the system came up saying "Restoring your previous version of Windows."

This is the same as it has been doing with the updates effectively.

When booted back up - the following error was on screen.




I am not sure where I can get any logs for you that might help, so please advise me if you need anything further from me to take this further. I have double checked the instructions and definitely followed them to the letter, so I have not missed out any steps.

I have noticed a new folder called "Windows10Upgrade" has appeared in the root of my C:\.

 

Run this version of the log collector and post a zip into the thread for troubleshooting:
log collector v2-beta08.zip

Download and install Everything search and use it to find these folders and files:
voidtools
For an files found use one drive or drop box share links to post into the thread.
Only post Panther files from the latest failure.


PANTHER logs
C:\Windows\Panther
setuperr.log
setupact.log
Setupmem.dmp
setupapi.dev.log
BlueBox.log
Event logs (*.evtx)
C:\$Windows.~BT\Sources\Rollback
$Windows.~bt\Sources\Rollback\setupmem.dmp
$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
$Windows.~bt\Sources\Rollback*.evtx
$Windows.~BT\Sources\Panther\UnattendGC
miglog.xml
Windows\Logs\Mosetup



The extend code was 30017
3 SP_EXECUTION_FIRST_BOOT
17 SP_EXECUTION_OP_BOOT

Installation failed during the FIRST_BOOT phase with an error during BOOT operation.


Resolve Windows 10 upgrade errors - Windows IT Pro | Microsoft Docs

 

Hi Zbook, thanks for continuing to look at this for me.

Here is the zip result from the log collector.
LASERBEAK (2018-01-22 14 58).zip

I have run the Everything Search and do not have some of the files that are in your list within my results - at least I cannot seem to see them. These are:
Setupmem.dmp
$Windows.~bt\Sources\Rollback\setupmem.dmp
$Windows.~bt\Sources\Rollback\setupapi\setupapi.dev.log
$Windows.~bt\Sources\Rollback*.evtx
$Windows.~BT\Sources\Panther\UnattendGC

The rest of the files I have placed in OneDrive here - there are some additional folders just in case you can spot the missing files, but I cannot:
PC Issues January 2018

Please let me know if you need anything else from me.

Thanks again.

 

In approximately 10 days there were approximately 14 crash dump failed.
The computer environment has been unstable.
Bitdefender was not completely uninstalled for the latest upgrade (see event log entries).

In the left lower corner search type: system > open system control panel > on the left pane click advanced system settings > under startup and recovery click settings > post an image into the thread.

> under performance click on settings > on performance options windows click on the advanced tab > under virtual memory click on change > post an image into the thread of the virtual memory tab

Download and install Whocrashed:
Resplendence Software - WhoCrashed, automatic crash dump analyzer

Uninstall Bitdefender:
Uninstall Bitdefender


Code: Event[5770]: Log Name: System Source: volmgr Date: 2018-01-22T12:29:52.560 Event ID: 46 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Laserbeak Description: Crash dump initialization failed![/quote] Code: Event[5420]: Log Name: System Source: Service Control Manager Date: 2018-01-22T11:02:54.179 Event ID: 7034 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Laserbeak Description: The Bitdefender Device Management Service service terminated unexpectedly. It has done this 1 time(s). Event[5421]: Log Name: System Source: Service Control Manager Date: 2018-01-22T11:02:54.180 Event ID: 7034 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Laserbeak Description: The Bitdefender Product Agent Service service terminated unexpectedly. It has done this 1 time(s). Event[5422]: Log Name: System Source: Service Control Manager Date: 2018-01-22T11:02:54.211 Event ID: 7031 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Laserbeak Description: The Bitdefender RedLine Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. Event[5423]: Log Name: System Source: Service Control Manager Date: 2018-01-22T11:02:54.273 Event ID: 7034 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Laserbeak Description: The Bitdefender Desktop Update Service service terminated unexpectedly. It has done this 1 time(s). Event[5424]: Log Name: System Source: Service Control Manager Date: 2018-01-22T11:03:54.222 Event ID: 7000 Task: N/A Level: Error Opcode: N/A Keyword: Classic User: N/A User Name: N/A Computer: Laserbeak Description: The Bitdefender RedLine Service service failed to start due to the following error: The system cannot find the path specified.[/quote]

 

Hi Zbook,

Yes, the instability is probably due to the failure of the updates to install as they have been trying and failing for around 2 weeks now.

Startup and Recovery Settings - hope this is the right place you wanted them from.




Virtual Memory Tab.




Who Crashed has been downloaded and installed - did you want me to run anything with it?
Bitdefender uninstall tool has been run again. Not sure why Bit Defender did not uninstall, the tool you linked to is the tool I used for the uninstall. I have run it again, and received the same confirmation as last time, so hopefully will have worked now.




Let me know if you need anything else from me. Thanks again.

 

For system failure > un-check automatically restart

After this has been modified perform a crash dump test with whocrashed.

Open Whocrashed > above analyze click on tools > crash dump test > type: ACCEPT

After the crash click Analyze > post the report into the thread

Run the log collector and post a new zip after the crash dump test:
log collector v2-beta08.zip

 

Ok - result of the crash test from Who Crashed is below.

Crash Dump Analysis
--------------------------------------------------------------------------------

Crash dumps are enabled on your computer.

Crash dump directories:
C:\Windows
C:\Windows\Minidump



On Mon 22/01/2018 16:48:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\Minidump\012218-12406-01.dmp
This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x19B4007E, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\Windows\system32\drivers\rspcrash64.sys
product: WhoCrashed
company: Resplendence Software Projects Sp.
description: Resplendence WhoCrashed Crash Dump Test
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.



On Mon 22/01/2018 16:48:53 your computer crashed or a problem was reported
crash dump file: C:\Windows\MEMORY.DMP
This was probably caused by the following module: rspcrash64.sys (rspCrash64+0x108B)
Bugcheck code: 0xDEADDEAD (0x0, 0x0, 0x19B4007E, 0x3C2A58ED)
Error: MANUALLY_INITIATED_CRASH1
file path: C:\Windows\system32\drivers\rspcrash64.sys
product: WhoCrashed
company: Resplendence Software Projects Sp.
description: Resplendence WhoCrashed Crash Dump Test
Bug check description: This indicates that the user deliberately initiated a crash dump from either the kernel debugger or the keyboard.
This bug check belongs to the crash dump test that you have performed with WhoCrashed or other software. It means that a crash dump file was properly written out.





--------------------------------------------------------------------------------
Conclusion
--------------------------------------------------------------------------------

2 crash dumps have been found and analyzed. No offending third party drivers have been found. Connsider using WhoCrashed Professional which offers more detailed analysis using symbol resolution. Also configuring your system to produce a full memory dump may help you.


Read the topic general suggestions for troubleshooting system crashes for more information.

Note that it's not always possible to state with certainty whether a reported driver is responsible for crashing your system or that the root cause is in another module. Nonetheless it's suggested you look for updates for the products that these drivers belong to and regularly visit Windows update or enable automatic updates for Windows. In case a piece of malfunctioning hardware is causing trouble, a search with Google on the bug check errors together with the model name and brand of your computer may help you investigate this further.

New zip from log collector.
*Replaced in later post with correct files*