Did some looking and I think you are making progress.
I would run the trouble shooter again and then follow the steps in Post 5 of this thread. This seems to be the more common fix for 80246010.
Problems with windows 10 installation Error 80246010
Weren't the MFT error and hive from over a year ago?
Yes both were old and were repaired.
Thanks for your help zbook. I followed your instructions completely. Here are the results.
1) For Ccleaner > un-check memory dumps and windows log files
2) For system failure > un-check automatically restart
3) For Windows error reporting change startup type to automatic > service status start > reboot
4) Upgrade BIOS: Version/Date American Megatrends Inc. F5, 4/21/15 > F6 9/18/2015
GA-Z97MX-Gaming 5 (rev. 1.0) | Motherboard - GIGABYTE U.S.A.
Last edited by zbook; 22 Dec 2017 at 20:19.
HI Ken I followed your advice by running troubleshooter again, and followed the steps in post 5 of that thread. When entering wuauclt.exe /updatenow in Command Prompt, this was the result.
Zbook I followed your instructions, but don't feel comfortable updating BIOS yet, since my pc is running smoothly. Also, I can't run these in command prompt:
1) dism /online /cleanup-image /checkhealth
2) dism /online /cleanup-image /scanhealth
3) dism /online /cleanup-image /restorehealth
4) sfc /scannow
because I get this result: "windows resource protection could not start the repair service".
Merry Xmas to all of you at Windows Ten Forums.
Okay.
Can you try the update from the USB key you created. Navigate to setup and double click.
1) open administrative command prompt and type or copy and paste:
net start trustedinstaller
2) sfc /scannow
3) dism /online /cleanup-image /checkhealth
4) 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
5) If you still get the same message: windows resource protection could not start the repair service then click on the left lower corner windows icon > click on power > continuously hold down the shift key while clicking restart > boot into safe mode
6) in safe mode open administrative command prompt and type: sfc /scannow
7) report into the thread whether you did or did not need to go into to safe mode and the result in safe mode for sfc /scannow
Hi
1. Make sure you have secured your present state before making major changes- create a full disk image of your existing Windows configuration (e.g. Macrium Reflect (free) ).
You don't want to end up with an unbootable non-recoverable PC.
(We constantly recommend people use disk imaging routinely as a matter of course).
2. Assuming your disk and file system are ok
Hard Disk Sentinel (trial)
From an admin prompt run
chkdsk c: \scan
- if repairs needed then run
chkdsk c: \f
(needs restart)
3. Then do an in-place upgrade repair install on 1607.
(Note: you will need to download or already have available the appropriate iso or bootable disk for 1607 - this can be downloaded e.g.
Microsoft Windows 10 Anniversary Update ISO 1607 Download • Windows ISO
or via MS Technet)
Repair Install Windows 10 with an In-place Upgrade Installation Upgrade Tutorials
Check you've more than 20Gb free on C:, and 1.5Gb of unallocated space on your system drive.
Disable or uninstall any AV; disconnect unnecessary peripherals.
4. Reattempt the upgrade.
5. If still no joy, post any error messages together with a screenshot of your partitions using Minitool Partition Wizard, expanding all columns as necessary to make sure text is visible.
Happy New Year to everyone at Ten Forums. Sorry I haven't responded earlier, I was away. First think I did was change my account login from local account to Microsoft account because I was reading that this has solved installing some stubborn updates.
https://answers.microsoft.com/en-us/...98f1507?auth=1
Next I followed the instructions in Post #18 from dalchina, and downloaded Version 1607 (my current version) to attempt a repair install. Next I started the install and initially said no to getting new updates as I wanted to repair my current version 1607 first. During the install nearing completion it asked again if I wanted to download and install new updates and this time I said yes. It took a while but everything installed perfectly. When I checked my version it now said Version 1709.
By doing the above steps it solved my problem. Many thanks again for your advice and knowledge.
That's great news.
Happy new year.
Quote
