Windows 10: chkdsk /f /r failure to fix errors

HP 17 Mobile Workstation Introduction - YouTube
http://h20628.www2.hp.com/km-ext/kmc...03916100-1.pdf

 

I am pretty much exhausted on this troubleshooting as its been so complex. The opportunity to get the new version seemed so fortunate as it may have fixed so many problems. However it failed with the error code 0xc1900200. Any chance you may now how to troubleshoot this error code? I saw something on the internet but cant locate it now. It was on the differences in partition requirements moving from 1607 to 1703. Could it possibly be that the partition is too small? I never have altered the size of a partition and don't know how. I did delete partitions using a windows 10 1607 bootable iso making a drive on another computer unallocated. Then I reinstalled version 1607. On that computer which had only a SSD drive the windows 10 1607 to 1703 worked smoothly.

This computer unfortunately I have not yet backed up or saved the files. If I had done that I would never have gone to the Microsoft store. Unfortunately my Seagate free agent goflex external hard drive proprietary USB adapter failed. It was half the cost of the whole hard drive. I was considering other options for backup but never figured out a good option for multiple computers.
Thanks for looking over the info. I didn't mean to overwhelm you but again I appreciate you look at.

 

I spoke with HP tech support about the thunderbolt services that was showing up in the control panel reliability and history and they did not have any other ideas than reinstalling the driver. They did not know why it was frequently listed there.

In the conversation I brought up the chkdsk corruption problems and the technician commented that that usually fixes itself after a boot. A boot was done and there was about a 5 minute wait before it got to the wall paper or lock screen. Then after log on to the desk top another chkdsk was ran. It displayed no corruption and no orphaned files.

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>chkdsk
The type of the file system is NTFS.

WARNING! /F parameter not specified.
Running CHKDSK in read-only mode.

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

Stage 2: Examining file name linkage ...
620088 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.
42781 data files processed.
CHKDSK is verifying Usn Journal...
34287064 USN bytes processed.
Usn Journal verification completed.

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

731466863 KB total disk space.
278906032 KB in 255322 files.
161372 KB in 42782 indexes.
0 KB in bad sectors.
662967 KB in use by the system.
65536 KB occupied by the log file.
451736492 KB available on disk.

4096 bytes in each allocation unit.
182866715 total allocation units on disk.
112934123 allocation units available on disk.

C:\WINDOWS\system32>

The windows update error seems to be related to partition sizing. Apparently each manufacturer has a different available size even though the partition size may have the same number. One thread recommended expanding the size of the partition from 100 MB to 250 MB to allow sufficient room for the windows update.

I'll be looking more into this windows update problem.

 

I got confirmation that the recovery partition is of insufficient size for upgrading windows 10 1607 to 1703. Diskpart can be used to expand the partition. The files are NOT backed up. Doesn't diskpart expansion put files at risk? What software (form downloads.com etc) if any can increase the recovery size partition so that an upgrade can be performed from 1607 to 1703?

 

We would have to see a full screenshot of disk management to offer accurate advice:
Disk Management - How to Post a Screenshot of - Windows 10 General Tips Tutorials

or a diskpart output. This is mine which has upgraded from 1607 to 1703 with no problems:

Code: Microsoft Windows [Version 10.0.15063] (c) 2017 Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>diskpart Microsoft DiskPart version 10.0.15063.0 Copyright (C) Microsoft Corporation. On computer: JOHN-LAPTOP DISKPART> list disk Disk ### Status Size Free Dyn Gpt -------- ------------- ------- ------- --- --- Disk 0 Online 447 GB 9 MB * Disk 1 Online 931 GB 2048 KB * Disk 2 No Media 0 B 0 B DISKPART> select disk 0 Disk 0 is now the selected disk. DISKPART> list part Partition ### Type Size Offset ------------- ---------------- ------- ------- Partition 1 System 100 MB 1024 KB Partition 2 Reserved 16 MB 101 MB Partition 3 Primary 446 GB 121 MB Partition 4 Recovery 825 MB 446 GB[/quote]

 

On my post just before this one I made a mistake typing "recovery partition". That should have just been partition.

When windows updates and then produces a failure code log files can be found in a similar fashion as CBS for sfc scannow.

These are the log files:

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

This is the disk management:

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

This is some information using diskpart: One of the volumes was labeled to see its contents. This diskpart was used to evaluate a different volume than the above windows update volume. If you think it would be useful I could use diskpark to label this volume. Please list the instructions as I am a relatively new user of diskpart.

Microsoft OneDrive - Access files anywhere. Create docs with free Office Online.

In the windows update failure log this is the entry that indicated the problem of the partition sizing:

2017-04-06 05:03:00, Info***************** CONX** CFreeSystemPartitionDiskSpaceChecker: checked InsufficientSystemPartitionDiskSpace, found HardBlock.Not enough space on partition [\\?\GLOBALROOT\Device\HarddiskVolume2\] Required: 15 MB. Available: 6 MB.


!) can diskpart be used to expand partitions without placing files at risk?
The files are not yet backed up.
If expansion of the partition using diskpart places files at risk is there any other software that may protect the files and allow expansion of the partition?

 

You should *NEVER, EVER* mess with partitioning on a disk without first making a complete backup, or better still, a complete backup and an image backup as well. If anything goes wrong during disk partitioning, it's at least possible that you might not otherwise be able to recover the disk contents affected thereby. The first step in moving, resizing, or otherwise messing about with disk partitions should ALWAYS be a backup/image backup.
HTH,
--Ed--