Cannot get Windows 10 to update.

[Rsun]

I did the pre scan and it informed me that these files were corrupt, damaged, had bad signatures, etc.  and it seems this is keeping me from updating past 10586.494.  I have read the msft forums and nothing has helped.  I ran the windows repair program and it did not fix my windows update problem.  How do I repair or download these 19 files?  Is something else wrong as well? 

C:\WINDOWS\servicing\Packages\Microsoft-OneCore-Analog-PerceptionApi-Stub-WOW64-Package~31bf3856ad364e35~amd64~~10.0.10586.0.cat
C:\WINDOWS\servicing\Packages\Microsoft-OneCore-AppRuntime-windows-Package~31bf3856ad364e35~amd64~~10.0.10586.0.cat
C:\WINDOWS\servicing\Packages\Microsoft-Windows-Client-Features-Package-AutoMerged-ds~31bf3856ad364e35~amd64~~10.0.10586.0.cat
C:\WINDOWS\servicing\Packages\Microsoft-Windows-Media-Streaming-WOW64-multimedia-Package~31bf3856ad364e35~amd64~en-US~10.0.10586.0.cat
C:\WINDOWS\servicing\Packages\Microsoft-Windows-Network-Security-CmdTools-WOW64-Package~31bf3856ad364e35~amd64~en-US~10.0.10586.0.cat
C:\WINDOWS\servicing\Packages\Package_1302_for_KB3140768~31bf3856ad364e35~amd64~~10.0.1.3.cat
C:\WINDOWS\servicing\Packages\Package_1339_for_KB3140768~31bf3856ad364e35~amd64~~10.0.1.3.cat
C:\WINDOWS\servicing\Packages\Package_1435_for_KB3140768~31bf3856ad364e35~amd64~~10.0.1.3.cat
C:\WINDOWS\servicing\Packages\Package_442_for_KB3140768~31bf3856ad364e35~amd64~~10.0.1.3.cat
C:\WINDOWS\servicing\Packages\Microsoft-OneCore-Analog-PerceptionApi-Stub-WOW64-Package~31bf3856ad364e35~amd64~~10.0.10586.0.mum
C:\WINDOWS\servicing\Packages\Microsoft-OneCore-AppRuntime-windows-Package~31bf3856ad364e35~amd64~~10.0.10586.0.mum
C:\WINDOWS\servicing\Packages\Microsoft-OneCore-CoreSystem-com-Package~31bf3856ad364e35~amd64~~10.0.10586.0.mum
C:\WINDOWS\servicing\Packages\Microsoft-Windows-Client-Features-Package-AutoMerged-ds~31bf3856ad364e35~amd64~~10.0.10586.0.mum
C:\WINDOWS\servicing\Packages\Microsoft-Windows-Media-Streaming-WOW64-multimedia-Package~31bf3856ad364e35~amd64~en-US~10.0.10586.0.mum
C:\WINDOWS\servicing\Packages\Microsoft-Windows-Network-Security-CmdTools-WOW64-Package~31bf3856ad364e35~amd64~en-US~10.0.10586.0.mum
C:\WINDOWS\servicing\Packages\Package_1302_for_KB3140768~31bf3856ad364e35~amd64~~10.0.1.3.mum
C:\WINDOWS\servicing\Packages\Package_1339_for_KB3140768~31bf3856ad364e35~amd64~~10.0.1.3.mum
C:\WINDOWS\servicing\Packages\Package_1435_for_KB3140768~31bf3856ad364e35~amd64~~10.0.1.3.mum
C:\WINDOWS\servicing\Packages\Package_442_for_KB3140768~31bf3856ad364e35~amd64~~10.0.1.3.mum

[Boggin]

The Cat and Mum file replacement section has now been closed because of the evolving Win 10 and the time it was taking to dig them out and upload them.

I'd suggest doing a manual update to v1607 rather than going straight for the latest 1703 update and wait for that to come through Windows Update.

In the following article, hover over Win 10 in the menu bar and then over AU 1607 and click on Standard.

http://windowsiso.net/

Select Save on the download and then you can use Windows USB/DVD Burner Tool to create either a bootable DVD or USB.

http://wudt.codeplex.com/

From within Windows open Windows Explorer - This PC - insert the install media and double click on the drive.

If using a DVD, that will start the process but if using an USB, that will open the files where you need to double click on the setup Application.

That should be successful, but run the Pre-Scan again to see if it still reports that corruption.

After the update, go into System Protection to see if it is still turned on.

JFI - When updating from one version to another, you have 10 days to roll back, but as a belt 'n braces you could create a full system image onto external media before the update as a fall back.

[Rsun]

Thank you very much, I will try this as soon as I can.  I have never created a full system image but I will learn and do that as well.

[Boggin]

For the system image, open Control Panel and under System and Security click on Back up and Restore (Windows 7) where you will see the link in the left pane for Create a system image.

I normally use an external HDD for those and create one onto alternate ext. HDDs each month after Windows Updates, Flash Player (on Win 7 laptop) and other programs that get updates around that time.

I plug the ext. HDD in before I click on Create a system image so that it can find the media to save it to, but you can also use DVDs.

System images can be useful for pulling you out of the mire when things get screwed up and also to restore your system onto a new HDD when the old one fails, as they can do - so it is advisable to get into the habit of regularly creating these.

[Rsun]

Thanks for laying that out for me, I will do it. 

Unfortunately, the 1607 installation failed.  I tried 3 times and even made a new DVD from a fresh download with no anti virus just in case and it still failed.  I also ran reimage PC scan and repair twice in between my attempts to update because it found issues with a couple of programs and wanted me to run it, all issues were fixed but still no ability to update.  I neglected to write down the programs, didn't think of it at the time.

I did not check the System Protection, I do not know how to do this.  When I have attempted to run scan now I think it is,  the System Protection always stopped the scan at 29%.     

[Boggin]

At which point did 1607 fail ?

Can you open a Command Prompt (Admin) and enter chkdsk /r

Enter y when prompted then enter shutdown /r /t 00  and wait for the chkdsk to execute after the reboot.

When it has completed and the machine has rebooted, right click on the Start Button and select Event Viewer.

When it has read the data, expand Windows Logs and click on Applications then look for a Wininit entry in the top scrollable pane and click on that.

You can then view the chkdsk report in the scrollable pane below.

As well as looking to see if it has repaired anything, check to see if it reports any KBs in bad sectors.

I'm always wary of programs like Reimage.

To check if System Protection is turned on, open Windows Explorer - right click on This PC and select Properties and then click on System protection in the left pane.

When it opens, it should say on for the volume drive letter.

 

[Rsun]

Sorry for not getting back to you, got busy and could not get to it yet.  I hope to try your next fix soon, thanks.

[Boggin]

If the chkdsk /r comes back clean, then see if the Update now button in this article will update you to the Creators Update (1703).

The chkdsk /r won't do anything for those missing/corrupt Package files but should eliminate any other problems.

The only way I know how to get around those is the option in the Pro version of Windows Repair, but don't update to v.4.0 just yet as Shane is releasing a v.4.01 tomorrow.

https://www.microsoft.com/en-gb/software-download/windows10

[Rsun]

I did the check disk and did not see any winit file to click on.  There were quite a few dll problems and there was two warnings that were both the same:

Log Name:      Application
Source:        Microsoft-Windows-Perflib
Date:          7/31/2017 11:05:01 AM
Event ID:      2003
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      Lenovo-PC
Description:
The configuration information of the performance library "C:\Windows\System32\perfts.dll" for the "TermService" service does not match the trusted performance library information stored in the registry. The functions in this library will not be treated as trusted.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Perflib" Guid="{13B197BD-7CEE-4B4E-8DD0-59314CE374CE}" EventSourceName="Perflib" />
    <EventID Qualifiers="32768">2003</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-07-31T18:05:01.671920600Z" />
    <EventRecordID>87106</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Lenovo-PC</Computer>
    <Security />
  </System>
  <UserData>
    <EventXML xmlns="Perflib">
      <param1>C:\Windows\System32\perfts.dll</param1>
      <param2>TermService</param2>
    </EventXML>
  </UserData>
</Event>

[Rsun]

This was another warning and I have seen this file come up with troubles lately.

Log Name:      Application
Source:        Application Error
Date:          7/31/2017 10:12:10 AM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Lenovo-PC
Description:
Faulting application name: TiWorker.exe, version: 10.0.10586.0, time stamp: 0x5632d7fd
Faulting module name: ntdll.dll, version: 10.0.10586.306, time stamp: 0x571af2eb
Exception code: 0xc0000420
Fault offset: 0x00000000000a4ab0
Faulting process id: 0x24f0
Faulting application start time: 0x01d309a5036d695a
Faulting application path: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10586.870_none_7645b64e266be2c8\TiWorker.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 8adf7670-eb10-477c-aa97-e7d0cdb0ff19
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-07-31T17:12:10.059158300Z" />
    <EventRecordID>87018</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Lenovo-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>TiWorker.exe</Data>
    <Data>10.0.10586.0</Data>
    <Data>5632d7fd</Data>
    <Data>ntdll.dll</Data>
    <Data>10.0.10586.306</Data>
    <Data>571af2eb</Data>
    <Data>c0000420</Data>
    <Data>00000000000a4ab0</Data>
    <Data>24f0</Data>
    <Data>01d309a5036d695a</Data>
    <Data>C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.10586.870_none_7645b64e266be2c8\TiWorker.exe</Data>
    <Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
    <Data>8adf7670-eb10-477c-aa97-e7d0cdb0ff19</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

[Rsun]

I have tried the creators update now before but I will give it another try. 

[Boggin]

To view the chkdsk log in Event Viewer, expand Windows Logs then click on Application.

If you do that straight after the chkdsk then you can scroll down the top pane until you see Wininit.

However, to locate it otherwise, after clicking on Application click on Action/Find then type chkdsk or wininit into the Find box and press enter.

Cancel the Find box and read the log in the scrollable pane.

For the first Event error, create a restore point then open a Command Prompt (Admin) and enter lodctr /T:TermService

This was courtesy of Google, but I don't know the significance of that error.

However, the second one could be the cause of your updating problems, but see how you get on with updating to 1703 (Curators Update).

[Rsun]

I will run chkdsk again and get the log so you can read it.  I think I understand better how to do this. 

I ran the creators update and it failed once again.

Do you think the pro version of the windows repair program would fix my problem?

[Boggin]

It should sort out those Package problems - whether that is related to the TiWorker.exe error - I don't know but I'll ask if you want to hang on from the purchase, but those Package errors can affect updates and I would buy it just for that repair.

How far did the update get to and how did you do it ?

[donnasander]

If you just do the manual update, it will usually (after it updates) also fix the update issue, and in short time, you can go back to automatic updating. I actually liked it better...on my own terms and solved 4 computer update issues for me so far.
http://www.techadvisor.co.uk/download/operating-systems-distros/wsus-offline-update-1101-3249902/

[Rsun]

I used the link that you provided and the button for updating not media creation disk.  I tried that too and it failed usually at about 50%

I ran the check disk and had success this time here it is:

Log Name:      Application
Source:        Microsoft-Windows-Wininit
Date:          7/31/2017 5:52:45 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      Lenovo-PC
Description:


Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows8_OS.

A disk check has been scheduled.
Windows will now check the disk.                         

Stage 1: Examining basic file system structure ...
  1463040 file records processed.                                                       

File verification completed.
  13764 large file records processed.                                   

  0 bad file records processed.                                     


Stage 2: Examining file name linkage ...
  1578852 index entries processed.                                                       

Index verification completed.
  0 unindexed files scanned.                                       

  0 unindexed files recovered to lost and found.                   


Stage 3: Examining security descriptors ...
CHKDSK is compacting the security descriptor stream
Cleaning up 6735 unused security descriptors.
  57907 data files processed.                                           

CHKDSK is verifying Usn Journal...
  36374544 USN bytes processed.                                                           

Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
  1463024 files processed.                                                               

File data verification completed.

Stage 5: Looking for bad, free clusters ...
  183386069 free clusters processed.                                                       

Free space verification is complete.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

 949227519 KB total disk space.
 213271168 KB in 1358562 files.
    804176 KB in 57910 indexes.
         0 KB in bad sectors.
   1607895 KB in use by the system.
     65536 KB occupied by the log file.
 733544280 KB available on disk.

      4096 bytes in each allocation unit.
 237306879 total allocation units on disk.
 183386070 allocation units available on disk.

Internal Info:
00 53 16 00 42 9c 15 00 33 37 2a 00 00 00 00 00  .S..B...37*.....
69 02 00 00 97 5c 00 00 00 00 00 00 00 00 00 00  i....\..........

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
    <EventID Qualifiers="16384">1001</EventID>
    <Version>0</Version>
    <Level>4</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2017-08-01T00:52:45.740797300Z" />
    <EventRecordID>87328</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>Lenovo-PC</Computer>
    <Security />
  </System>
  <EventData>
    <Data>

Checking file system on C:
The type of the file system is NTFS.
Volume label is Windows8_OS.

A disk check has been scheduled.
Windows will now check the disk.                         

Stage 1: Examining basic file system structure ...
  1463040 file records processed.                                                       

File verification completed.
  13764 large file records processed.                                   

  0 bad file records processed.                                     


Stage 2: Examining file name linkage ...
  1578852 index entries processed.                                                       

Index verification completed.
  0 unindexed files scanned.                                       

  0 unindexed files recovered to lost and found.                   


Stage 3: Examining security descriptors ...
CHKDSK is compacting the security descriptor stream
Cleaning up 6735 unused security descriptors.
  57907 data files processed.                                           

CHKDSK is verifying Usn Journal...
  36374544 USN bytes processed.                                                           

Usn Journal verification completed.

Stage 4: Looking for bad clusters in user file data ...
  1463024 files processed.                                                               

File data verification completed.

Stage 5: Looking for bad, free clusters ...
  183386069 free clusters processed.                                                       

Free space verification is complete.
Correcting errors in the master file table's (MFT) BITMAP attribute.
Correcting errors in the Volume Bitmap.

Windows has made corrections to the file system.
No further action is required.

 949227519 KB total disk space.
 213271168 KB in 1358562 files.
    804176 KB in 57910 indexes.
         0 KB in bad sectors.
   1607895 KB in use by the system.
     65536 KB occupied by the log file.
 733544280 KB available on disk.

      4096 bytes in each allocation unit.
 237306879 total allocation units on disk.
 183386070 allocation units available on disk.

Internal Info:
00 53 16 00 42 9c 15 00 33 37 2a 00 00 00 00 00  .S..B...37*.....
69 02 00 00 97 5c 00 00 00 00 00 00 00 00 00 00  i....\..........

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
  </EventData>
</Event>

[Rsun]

Now that I did the check correctly I will try to update manually again and if it does not work I will purchase the program and see if that fixes it.  Any other ideas?

[donnasander]

if you use the WSUS offline updater, it's free, you don't have to buy it, it works EXTREMELY well. Fixed 4 machines I had that would not update. Seriously.

So from looking at your log, you have a disk Volume Label Windows 8 OS, but it's actually Windows 10PC? so it was an upgrade in place from windows 8 (or 8.1) to windows 10? You should eventually back up your data, and just do a clean install...it will work SO much nicer. Upgrades just never work real well. Seeing how many file changed made to the table, you may have to do that.

in addition to chkdsk, you can also run scandisk which checks operating system files. (chkdsk just checks the disk)

in an elevated command prompt, at the end of the prompt, type sfc /scannow   ...and let it run, and see what happens. Post back...

[Boggin]

A sfc /scannow doesn't check all files and won't do anything for those corrupt Package files.

I try to leave a clean install as a last resort so as to minimize the work that can be involved.

I've used WSUS Offline Update before but it depends upon what is the cause of the updates not working.

[Boggin]

@ Rsun - Did you execute that command that I'd posted in my Reply #11 ?