Page 6 of 7 FirstFirst ... 4567 LastLast
  1.    07 Jun 2017 #51
    Join Date : Nov 2015
    Posts : 2,863
    64bit Win 10 Pro ver 1709 Build 16299.64

    I'll let @dalchina comment on why he suggested 700MB, but it would be enough for one new recovery partition. Placing at the end is fine IMO.

    A restart before creating a system image is a good precaution. The image backup process is clever, it creates a snapshot of the system but you can carry on working and it will collect up any new changes you make before it finally writes the new system image backup.
      My ComputersSystem Spec
  2.    07 Jun 2017 #52
    Join Date : Mar 2016
    Posts : 162
    Microsoft Windows 10 Pro 64-bit
    Thread Starter

    Quote Originally Posted by philc43 View Post
    A restart before creating a system image is a good precaution. The image backup process is clever, it creates a snapshot of the system but you can carry on working and it will collect up any new changes you make before it finally writes the new system image backup.
    So it falls into the category of "probably unnecessary, but still a good idea"?

    EDIT: After writing this post, I decided to try creating a differential backup. It took only about five minutes (including verification, and created a small file (4 GB). I can see the benefits now. dalchina, thank you for recommending it to me.

    I think I'll attempt to add the unallocated space tomorrow.
    Last edited by hbenthow; 07 Jun 2017 at 01:55.
      My ComputerSystem Spec
  3.    07 Jun 2017 #53
    Join Date : Jan 2015
    UK, Midlands
    Posts : 10,971
    Win 10 Pro (1703)

    Sounds good. The unallocated space is just a pragmatic measure. Normally Recovery partitions for EFI installations are 450Mb, 500Mb for legacy BIos, which yours appears to be. So 700Mb..

    I found my second recovery partition appeared after doing an in-place upgrade repair install.

    If there isn't room on your system disk, but is elsewhere, the partition can be created on a different disk- messy.

    Quite why this happens is unclear- I did once find a bit of MS text on that.
      My ComputerSystem Spec
  4.    07 Jun 2017 #54
    Join Date : Mar 2016
    Posts : 162
    Microsoft Windows 10 Pro 64-bit
    Thread Starter

    Quote Originally Posted by dalchina View Post
    Sounds good. The unallocated space is just a pragmatic measure. Normally Recovery partitions for EFI installations are 450Mb, 500Mb for legacy BIos, which yours appears to be. So 700Mb..
    The reason why I'm wondering whether it might be better to create room for more than one recovery partition is that I don't know whether Windows will create more than one.

    What I mean is this: I don't know whether it's possible that the next major update (such as the Creators Upgrade) will create another 500 MB recovery partition in addition to the one that I have now, then the next update after it will try to create a third. It's because of that hypothetical third recovery partition that I'm wondering whether I should make the unallocated space larger than 700 MB. Should this be a concern?
      My ComputerSystem Spec
  5.    07 Jun 2017 #55
    Join Date : Jan 2015
    UK, Midlands
    Posts : 10,971
    Win 10 Pro (1703)

    Reckon on 2 max. You can always remove the unused one.
      My ComputerSystem Spec
  6.    07 Jun 2017 #56
    Join Date : Mar 2016
    Posts : 162
    Microsoft Windows 10 Pro 64-bit
    Thread Starter

    Quote Originally Posted by dalchina View Post
    Reckon on 2 max. You can always remove the unused one.
    How would I be able to tell which was used and which was unused?
      My ComputerSystem Spec
  7.    07 Jun 2017 #57
    Join Date : Jan 2015
    UK, Midlands
    Posts : 10,971
    Win 10 Pro (1703)

    You need to use the reagentc and bcdedit commands at an admin command prompt.

    /? gives help

    E.g.
    reagentc /?
      My ComputerSystem Spec
  8.    07 Jun 2017 #58
    Join Date : Mar 2016
    Posts : 162
    Microsoft Windows 10 Pro 64-bit
    Thread Starter

    Quote Originally Posted by dalchina View Post
    You need to use the reagentc and bcdedit commands at an admin command prompt.

    /? gives help

    E.g.
    reagentc /?
    And that would tell me which one I need to keep?

    I'm currently defragmenting the drive in preparation to creating the unallocated space. Are there any other last-minute things I should know before going ahead and creating it?
      My ComputerSystem Spec
  9.    07 Jun 2017 #59
    Join Date : Jan 2015
    UK, Midlands
    Posts : 10,971
    Win 10 Pro (1703)

    Win 10 takes care of routine defrag. Shouldn't be necessary, really.

    Always safest to update your disk image before making changes, though this is relatively trivial.

    You'd need info from both to work out the relevant partition number.
      My ComputerSystem Spec
  10.    07 Jun 2017 #60
    Join Date : Mar 2016
    Posts : 162
    Microsoft Windows 10 Pro 64-bit
    Thread Starter

    Quote Originally Posted by dalchina View Post
    Win 10 takes care of routine defrag. Shouldn't be necessary, really.
    The defragmentation didn't take long. Afterward, I started up AOMEI and (as the AOMEI website recommended) selected my Windows partition, went to "Advanced", then selected "Check Partition", then ran it with the option "Check partition for errors by using chkdsk.exe" selected. (This is to make sure that there are no problems with the drive or its file system, prior to using AOMEI to alter partitions.)

    It ran a quick scan of the partition, and unfortunately found some errors.
    Here are the results:
    Attachment 138456

    It says that I can fix them using AOMEI, but I'm wondering whether that's thorough enough. Do you think that I should try to fix it with AOMEI, or would it be better to run a full chkdsk C: /f / /r /x command through Command Prompt? Or should I do the former, then the latter to be sure of getting any leftover errors?

    Also, do you happen to know what this particular error is a symptom of? How serious could this be?

    EDIT: I decided to go ahead and let AOMEI try to fix it. After selecting that option, the computer restarted and went through a CHKDSK session, at the end of which it said that it had finished checking for a and fixing errors. Once I booted back into Windows after CHKDSK finished, I checked the disc with AOMEI yet again. This time, it showed almost the same message as before, but this time with different files listed as having errors. So I again selected the option to let AOMEI try to fix it. The computer again restarted and went through a CHKDSK session, again claiming that it had finished checking for and fixing errors. I again booted into Windows and started up AOMEI. I again used it to check the partition. This time, it gave me this ominous-sounding message:

    Attachment 138457

    Take special notice of the part that says, "The master file table's (MFT) BITMAP attribute is incorrect. The Volume Bitmap is incorrect. Windows has checked the file system and found problems. Please run chkdsk /scan to find the problems and queue them for repair."

    I opened up an elevated command prompt and ran chkdsk /scan, with the following result:

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


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


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


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


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


    976146431 KB total disk space.
    96321096 KB in 312241 files.
    233428 KB in 68217 indexes.
    0 KB in bad sectors.
    568675 KB in use by the system.
    65536 KB occupied by the log file.
    879023232 KB available on disk.


    4096 bytes in each allocation unit.
    244036607 total allocation units on disk.
    219755808 allocation units available on disk.
    This is very troubling. AOMEI's message implied that the way to fix the errors that it found was to run chkdsk /scan. However, when I did so, it neither found nor corrected the errors, meaning that they are still there.

    Then, I decided to check the disc with AOMEI once again, and got this message:

    Checking (C: ), please wait a few seconds or minutes...-------------------------------------------------------------
    Volume label is Windows.


    Stage 1: Examining basic file system structure ...

    414720 file records processed.


    File verification completed.

    11758 large file records processed.



    0 bad file records processed.




    Stage 2: Examining file name linkage ...
    Index entry f_0019dd in index $I30 of file 67450 is incorrect.
    Index entry TransportSecurity in index $I30 of file 126169 is incorrect.
    Index entry TRANSP~1 in index $I30 of file 126169 is incorrect.
    Index entry etilqs_3Hy1jlzOXbrisVu in index $I30 of file 333284 is incorrect.
    Index entry ETILQS~3 in index $I30 of file 333284 is incorrect.
    Index entry the-real-index in index $I30 of file 378443 is incorrect.
    Index entry THE-RE~1 in index $I30 of file 378443 is incorrect.
    Index entry a77cc5d7cc40a365_0 in index $I30 of file 378447 is incorrect.
    Index entry A77CC5~1 in index $I30 of file 378447 is incorrect.
    Index entry todelete_c85599bd7115f7eb in index $I30 of file 378447 is incorrect.
    Index entry TODELE~1 in index $I30 of file 378447 is incorrect.
    Index entry the-real-index in index $I30 of file 378450 is incorrect.
    Index entry THE-RE~1 in index $I30 of file 378450 is incorrect.

    551146 index entries processed.


    Index verification completed.


    Errors found. CHKDSK cannot continue in read-only mode.


    Chkdsk has completed, but some errors were found in the partition.
    You could use AOMEI Partition Assistant to fix it.
    It appears that the errors are multiplying!

    I then decided to go to "This PC - Windows (C: ) - Right Click - Properties - Tools - Error Checking" in order to run a scan directly from Windows itself. I got the following result:

    Attachment 138464

    I clicked "Show Details", and was brought to the Event Viewer, which showed this information about the scan:

    [Log Name: ApplicationSource: Chkdsk
    Date: 6/7/2017 3:40:30 PM
    Event ID: 26226
    Task Category: None
    Level: Information
    Keywords: Classic
    User: N/A
    Computer: WINDOWS-SJ9IF72
    Description:
    Chkdsk was executed in scan mode on a volume snapshot.


    Checking file system on C:
    Volume label is Windows.


    Stage 1: Examining basic file system structure ...

    414720 file records processed.


    File verification completed.

    11758 large file records processed.



    0 bad file records processed.




    Stage 2: Examining file name linkage ...

    551150 index entries processed.


    Index verification completed.








    Stage 3: Examining security descriptors ...
    Security descriptor verification completed.

    68216 data files processed.


    CHKDSK is verifying Usn Journal...

    55868600 USN bytes processed.


    Usn Journal verification completed.


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


    976146431 KB total disk space.
    96322176 KB in 312243 files.
    233432 KB in 68217 indexes.
    569507 KB in use by the system.
    65536 KB occupied by the log file.
    879021316 KB available on disk.


    4096 bytes in each allocation unit.
    244036607 total allocation units on disk.
    219755329 allocation units available on disk.


    ----------------------------------------------------------------------




    Stage 1: Examining basic file system structure ...


    Stage 2: Examining file name linkage ...


    Stage 3: Examining security descriptors ...


    Windows has scanned the file system and found no problems.
    No further action is required.
    Apparently, it can't find the errors either (much less provide a solution for them).

    What should I do? Is there anything that I can do? Is my system too corrupted to fix?
    Last edited by hbenthow; 07 Jun 2017 at 17:23.
      My ComputerSystem Spec

 
Page 6 of 7 FirstFirst ... 4567 LastLast


Similar Threads
Thread Forum
System restore - weird behavior
I seem to be running into some odd behavior with system restore. I wanted to delete my old restore points and create a new one. So under system restore>configure, I selected delete. The "current usage" dropped to 0 GB. But when I closed it and went...
Backup and Restore
Weird behavior, possible Trojan
Symptoms: 1. Volume icon appears with a red cross even though all sound devices are working. 2. With UAC set to default, a notification pops up at startup asking my permission to run explorer.exe 3. I can't run some programs. 4. Malwarebytes web...
AntiVirus, Firewalls and System Security
In Windows 10, weird window behavior...
The only reason I'm using Windows at all, (and not using Linux), is Windows is the only OS that's "handicap accessible" for people with my type of eye problems. I have very poor eyesight... and without the magnifier, I can't use the computer at...
General Support
Weird behavior after update
I had a recent update of win10. After that everything is ok except when I launch applications a small window with an html file open with the buttons save and open. If I open they open in the browser but nothing happen if I save them the same because...
General Support
Weird windows 10 behavior
Just wonder if anyone has encountered these behaviors? It happens to me every time without exception: If I do a restart, the computer restarts but makes the windows 7-start sound. Upon getting to the desktop, the laptop battery meter is missing...
General Support
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 23:23.
Find Us
Twitter Facebook Google+ Ten Forums iOS App Ten Forums Android App



Windows 10 Forums