chkdsk errors "/F parameter not specified"

Page 1 of 2 12 LastLast

  1. Posts : 158
    10 Home x64 v22H2
       #1

    chkdsk errors "/F parameter not specified"


    I recently changed my boot partition so I was able to safe boot, but after trying to merge my old partition with my boot drive (MiniTool), it failed and my BIOS reset. Ran chkdsk and it seems I have a few errors. It doesn't seem like I'm able to resolve these with sfc /scannow because "/F parameter not specified", and I'm not sure about using MiniTool yet until I figure out if these things are even related. Never did a chkdsk in the past year, really these could have been laying around forever for all I know.
    Code:
    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 ...                                                                                                                                                                  
    527448 file records processed. 
    File verification completed.
    
    File record segment 7F2F5 is an orphan.File record segment 7F2F6 is an orphan.File record segment 7F2F7 is an orphan.File record segment 7F2FD is an orphan.File record segment 7F2FF is an orphan.File record segment 7F300 is an orphan.File record segment 7F301 is an orphan.File record segment 7F302 is an orphan.File record segment 7F306 is an orphan.File record segment 7F309 is an orphan.File record segment 7F30B is an orphan.File record segment 7F30C is an orphan.File record segment 7F30E is an orphan.File record segment 7F310 is an orphan.File record segment 7F314 is an orphan.File record segment 7F315 is an orphan.File record segment 7F316 is an orphan.File record segment 7F31A is an orphan.File record segment 7F31B is an orphan.File record segment 7F31E is an orphan.File record segment 7F31F is an orphan.File record segment 7F320 is an orphan.File record segment 7F323 is an orphan.File record segment 7F325 is an orphan.File record segment 7F327 is an orphan.File record segment 7F329 is an orphan.File record segment 7F32A is an orphan.File record segment 7F32B is an orphan.File record segment 7F32F is an orphan.File record segment 7F331 is an orphan.File record segment 7F332 is an orphan.File record segment 7F334 is an orphan.File record segment 7F336 is an orphan.File record segment 7F337 is an orphan.File record segment 7F33A is an orphan.File record segment 7F33C is an orphan.File record segment 7F340 is an orphan.File record segment 7F341 is an orphan.File record segment 7F342 is an orphan.File record segment 7F343 is an orphan.File record segment 7F34B is an orphan.File record segment 7F34D is an orphan.File record segment 7F34F is an orphan.File record segment 7F357 is an orphan.File record segment 7F359 is an orphan.File record segment 7F35A is an orphan.File record segment 7F35B is an orphan.File record segment 7F35C is an orphan.File record segment 7F35D is an orphan.File record segment 7F35F is an orphan.File record segment 7F361 is an orphan.File record segment 7F365 is an orphan.File record segment 7F366 is an orphan.File record segment 7F367 is an orphan.File record segment 7F368 is an orphan.File record segment 7F36A is an orphan.File record segment 7F36B is an orphan.File record segment 7F36D is an orphan.File record segment 7F36E is an orphan.File record segment 7F36F is an orphan.File record segment 7F370 is an orphan.File record segment 7F378 is an orphan.File record segment 7F379 is an orphan.File record segment 7F37D is an orphan.File record segment 7F37E is an orphan.File record segment 7F380 is an orphan.File record segment 7F382 is an orphan.File record segment 7F384 is an orphan.File record segment 7F389 is an orphan.File record segment 7F38A is an orphan.File record segment 7F38B is an orphan.File record segment 7F38F is an orphan.File record segment 7F390 is an orphan.File record segment 7F392 is an orphan.File record segment 7F396 is an orphan.File record segment 7F397 is an orphan.File record segment 7F398 is an orphan.File record segment 7F399 is an orphan.File record segment 7F39B is an orphan.File record segment 7F39C is an orphan.File record segment 7F3A0 is an orphan.File record segment 7F3A2 is an orphan.File record segment 7F3A3 is an orphan.File record segment 7F3A8 is an orphan.File record segment 7F3A9 is an orphan.File record segment 7F3AB is an orphan.File record segment 7F3AE is an orphan.File record segment 7F3AF is an orphan.File record segment 7F3B0 is an orphan.File record segment 7F3B2 is an orphan.File record segment 7F3B8 is an orphan.File record segment 7F3B9 is an orphan.File record segment 7F3BB is an orphan.File record segment 7F3BC is an orphan.File record segment 7F3BE is an orphan.File record segment 7F3C0 is an orphan.File record segment 7F3C1 is an orphan.File record segment 7F3C2 is an orphan.File record segment 7F3C8 is an orphan.File record segment 7F3CA is an orphan.File record segment 7F3CB is an orphan.File record segment 7F3CC is an orphan.File record segment 7F3CD is an orphan.File record segment 7F3D0 is an orphan.File record segment 7F3D1 is an orphan.File record segment 7F3D2 is an orphan.File record segment 7F3D3 is an orphan.File record segment 7F3D4 is an orphan.File record segment 7F3D6 is an orphan.File record segment 7F3D7 is an orphan.File record segment 7F3D8 is an orphan.File record segment 7F3DB is an orphan.File record segment 7F3DC is an orphan.File record segment 7F3DE is an orphan.File record segment 7F3DF is an orphan.File record segment 7F3E1 is an orphan.File record segment 7F3E5 is an orphan.File record segment 7F3E6 is an orphan.File record segment 7F3ED is an orphan.File record segment 7F3EE is an orphan.File record segment 7F3EF is an orphan.File record segment 7F3F0 is an orphan.File record segment 7F3F3 is an orphan.File record segment 7F3F4 is an orphan.File record segment 7F3F7 is an orphan.File record segment 7F3F8 is an orphan.File record segment 7F3F9 is an orphan.File record segment 7F3FA is an orphan.File record segment 7F3FB is an orphan.File record segment 7F3FC is an orphan.File record segment 7F3FD is an orphan.File record segment 7F400 is an orphan.File record segment 7F402 is an orphan.File record segment 7F405 is an orphan.File record segment 7F406 is an orphan.File record segment 7F408 is an orphan.File record segment 7F409 is an orphan.File record segment 7F40A is an orphan.File record segment 7F40D is an orphan.File record segment 7F40E is an orphan.File record segment 7F40F is an orphan.File record segment 7F413 is an orphan.File record segment 7F414 is an orphan.File record segment 7F415 is an orphan.File record segment 7F416 is an orphan.File record segment 7F418 is an orphan.File record segment 7F41D is an orphan.File record segment 7F421 is an orphan.File record segment 7F423 is an orphan.File record segment 7F424 is an orphan.File record segment 7F426 is an orphan.File record segment 7F427 is an orphan.File record segment 7F428 is an orphan.File record segment 7F42B is an orphan.File record segment 7F42C is an orphan.File record segment 7F42D is an orphan.File record segment 7F42F is an orphan.File record segment 7F431 is an orphan.File record segment 7F432 is an orphan.File record segment 7F433 is an orphan.File record segment 7F437 is an orphan.File record segment 7F439 is an orphan.File record segment 7F43C is an orphan.File record segment 7F43E is an orphan.File record segment 7F43F is an orphan.File record segment 7F441 is an orphan.File record segment 7F442 is an orphan.File record segment 7F443 is an orphan.File record segment 7F444 is an orphan.File record segment 7F445 is an orphan.File record segment 7F446 is an orphan.File record segment 7F44C is an orphan.File record segment 7F44D is an orphan.File record segment 7F451 is an orphan.File record segment 7F454 is an orphan.File record segment 7F456 is an orphan.File record segment 7F457 is an orphan.File record segment 7F45A is an orphan.File record segment 7F45B is an orphan.File record segment 7F45C is an orphan.File record segment 7F460 is an orphan.File record segment 7F461 is an orphan.File record segment 7F462 is an orphan.File record segment 7F464 is an orphan.File record segment 7F466 is an orphan.File record segment 7F468 is an orphan.File record segment 7F46D is an orphan.File record segment 7F472 is an orphan.File record segment 7F473 is an orphan.File record segment 7F478 is an orphan.File record segment 7F47D is an orphan.File record segment 7F47E is an orphan.File record segment 7F47F is an orphan.File record segment 7F481 is an orphan.File record segment 7F491 is an orphan.File record segment 7F495 is an orphan.File record segment 7F499 is an orphan.File record segment 7F49B is an orphan.File record segment 7F49C is an orphan.File record segment 7F49E is an orphan.File record segment 7F49F is an orphan.File record segment 7F4A1 is an orphan.File record segment 7F4A2 is an orphan.File record segment 7F4A5 is an orphan.File record segment 7F4A7 is an orphan.File record segment 7F4A8 is an orphan.File record segment 7F4AB is an orphan.File record segment 7F4AD is an orphan.File record segment 7F4AE is an orphan.File record segment 7F4B0 is an orphan.File record segment 7F4B1 is an orphan.File record segment 7F4B2 is an orphan.File record segment 7F4B4 is an orphan.File record segment 7F4B6 is an orphan.File record segment 7F4B7 is an orphan.File record segment 7F4B8 is an orphan.File record segment 7F4BC is an orphan.                                                                                File record segment 7F4BD is an orphan.File record segment 7F4BF is an orphan.File record segment 7F4C0 is an orphan.File record segment 7F4C3 is an orphan.File record segment 7F4C4 is an orphan.File record segment 7F4C5 is an orphan.File record segment 7F4C7 is an orphan.File record segment 7F4C8 is an orphan.File record segment 7F4C9 is an orphan.File record segment 7F4CA is an orphan.File record segment 7F4CC is an orphan.File record segment 7F4CD is an orphan.File record segment 7F4CF is an orphan.File record segment 7F4DF is an orphan.File record segment 7F4E0 is an orphan.File record segment 7F4E1 is an orphan.File record segment 7F4E4 is an orphan.
    7116 large file records processed.File record segment 7F4E7 is an orphan.
    Errors found.  CHKDSK cannot continue in read-only mode.
    With sfc /scannow I get this.
    Code:
    Windows Resource Protection found corrupt files but was unable to fix some of them.
    For online repairs, details are included in the CBS log file located atwindir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offlinerepairs, details are included in the log file provided by the /OFFLOGFILE flag.
      My Computer


  2. Posts : 42,979
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2

    You would need to run e.g.
    chkdsk c: /F
    from an admin command prompt or powershell prompt to fix the chkdsk errors - and as those are file system errors, should be resolved before running SFC /SCANNOW.

    Your PC will need to restart.
    You can get the results thus:
    How Do I See the Results of a CHKDSK that Ran on Boot? - Ask Leo!

    You can check the syntax by launching a command prompt and then
    chkdsk /?
      My Computers


  3. Posts : 31,644
    10 Home x64 (22H2) (10 Pro on 2nd pc)
       #3

    Supra said:
    ...With sfc /scannow I get this.
    Code:
    Windows Resource Protection found corrupt files but was unable to fix some of them.
    For online repairs, details are included in the CBS log file located atwindir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline repairs, details are included in the log file provided by the /OFFLOGFILE flag.
    Strictly speaking this is not a BSOD issue and a Mod may move this thread to a more appropriate board.

    For your SFC errors, you can find out precisely what they are with Option Five in this tutorial.

    Run SFC Command in Windows 10

    If they are all Defender Powershell errors then it's a 'non-issue' caused by a known bug.

    Microsoft said:
    ...Because SFC incorrectly flags the files in %windir%\System32\WindowsPowerShell\v1.0\Modules\Defender, you can safely ignore the SFC error messages regarding these files.
    https://support.microsoft.com/en-us/...s-as-corrupted
      My Computers


  4. Posts : 158
    10 Home x64 v22H2
    Thread Starter
       #4

    Bree said:
    Strictly speaking this is not a BSOD issue and a Mod may move this thread to a more appropriate board.
    Apologies, I just read and debugging and assumed other things. Felt 'Hardware' is too general but it actually probably fits there better if so.

    Bree said:
    If they are all Defender Powershell errors then it's a 'non-issue' caused by a known bug.
    Copy that, that's what's in the details.

    dalchina said:
    You would need to run e.g.
    dalchina said:
    chkdsk c: /F

    from an admin command prompt or powershell prompt to fix the chkdsk errors - and as those are file system errors, should be resolved before running SFC /SCANNOW.


    Your PC will need to restart.
    You can get the results thus:
    How Do I See the Results of a CHKDSK that Ran on Boot? - Ask Leo!

    You can check the syntax by launching a command prompt and then
    chkdsk /?
    Great! This resolved the bad sectors. Not sure what to do about my partition merging issue, however.
      My Computer


  5. Posts : 42,979
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #5

    A small step on the way- good.

    Presumably SFC /SCANNOW problems remain?

    As regards your partitions, it's not clear what your current state is or what you're trying to do.. to me, anyway.

    Please use Minitool Partition Wizard (rather than Disk Manager); expand columns so all text is visible, post a screenshot using the Insert Image icon above your post, and explain what you'd like to achieve.

    Note that manipulating 'C:' should be done using a 3rd party tool.
    Last edited by dalchina; 13 Aug 2019 at 06:43.
      My Computers


  6. Posts : 158
    10 Home x64 v22H2
    Thread Starter
       #6

    dalchina said:
    Presumably SFC /SCANNOW problems remain?
    The SFC errors are all Windows Defender powershell ones that are apparently bugged.
    dalchina said:
    As regards your partitions, it's not clear what yor current state is or what you're trying to do.. to me, anyway.
    Have two system partitions; want to merge the old one into my C:\. MiniTool seems to fail with "not enough space". Thinking I should maybe make it so that it's unallocated then extend the boot partition to eat up the space.

    Attachment 243101
      My Computer


  7. Posts : 42,979
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #7

    Please post a screenshot using Minitool Partition Wizard, showing all your disks and their partitions, like this:
    Attachment 243108
    (I have only 1 disk in this PC)

    Please indicate which partitions you are considering merging.

    You say they are system partitions. Considering the one that is not your current Windows partition, what is its content? Your easy option should be to delete the unwanted partition, and exend the other into the new free space.

    Or do you need to keep the content?
      My Computers


  8. Posts : 158
    10 Home x64 v22H2
    Thread Starter
       #8

    dalchina said:
    Please indicate which partitions you are considering merging.
    Sorry, should've probably been less vague.

    Attachment 243109

    dalchina said:
    You say they are system partitions. Considering the one that is not your current Windows partition, what is its content?
    Just the EFI folder, I'm not sure why it says the drive is 64MB free out of 350 when the folder is 25MB (nothing hidden) but I imagine that's irrelevant.
      My Computer


  9. Posts : 42,979
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #9
      My Computers


  10. Posts : 158
    10 Home x64 v22H2
    Thread Starter
       #10

    I thought the BIOS was stored on the motherboard? The F:\ drive is my (new) system partition.
      My Computer


 

  Related Discussions
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 03:24.
Find Us




Windows 10 Forums