Share via


Diskpart: How do you troubleshoot: format quick fs=ntfs DiskPart has encountered an error: The parameter is incorrect.

Question

Tuesday, March 17, 2020 6:36 PM

Microsoft Windows [Version 10.0.18363.720]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\windows\system32>diskpart

Microsoft DiskPart version 10.0.18362.1

Copyright (C) Microsoft Corporation.
On computer: DESKTOP-K2CP43S

DISKPART> sel dis 0

Disk 0 is now the selected disk.

DISKPART> lis par

  Partition ###  Type              Size     Offset
       
  Partition 1    Primary            499 MB  1024 KB
  Partition 2    Primary            689 GB   500 MB
  Partition 3    Primary           2056 MB   689 GB
  Partition 4    Recovery          7148 MB   691 GB

DISKPART> sel par 4

Partition 4 is now the selected partition.

DISKPART> format quick fs=ntfs

    0 percent completed

DiskPart has encountered an error: The parameter is incorrect.
See the System Event Log for more information.

DISKPART>

All replies (4)

Wednesday, March 18, 2020 2:12 AM

Hi,

 

The parameter is incorrect usually occurs due to damaged file system, bad sectors and other various reasons.

 

You could run Check Disk utility to fix errors:

1.Open File Explorer.

2. Find the partition that needs fixing and right click it. Then, choose Properties.

3. In the pop-up mini window, click Check under Tools and click OK to continue.

4.Check “Automatically fix file system errors” and “Scan for and attempt recovery for bad sectors”. Then click Start button.

 

After performing disk check, you can try to format the partition again.

 

Best Regards,

Farena

Please remember to mark the replies as answers if they help.
"Windows 10 Installation, Setup, and Deployment" forum will be migrating to a new home on Microsoft Q&A (Preview)!
We invite you to post new questions in the "Windows 10 Installation, Setup, and Deployment" forum’s new home on Microsoft Q&A (Preview)!
For more information, please refer to the sticky post.


Wednesday, March 18, 2020 5:39 AM

The computer was booted using a Windows 10 iso.

In Windows RE command prompt diskpart was used to identify drive letters.

The chkdsk switches /b /v were used.

Each of the four partitions displayed windows found no problems.

Upon reboot to windows this administrative command prompt was ran:

format quick fs=ntfs

It again displayed:

0 percent completed

DiskPart has encountered an error: The parameter is incorrect.

Would it perform differently if format fs=ntfs were used instead?

What other troubleshooting options are there?


Wednesday, March 18, 2020 6:25 AM

Hi,

 

You could format the disk totally using Diskpart.

 

This way will erase all data on the disk. You can retrieve data to another place if necessary.

 

1. Run Diskpart as administrator.

 

2. Type the following commands and hit Enter after each command.

 

list disk

select disk n

# n refers to the disk number of the disk that you need to clean

 

clean

create partition primary

format fs=ntfs quick

assign drive letter=f

exit

 

If Diskpart has encountered an error: The parameter is incorrect still appears, replace “clean” with “clean all”.

Please remember to mark the replies as answers if they help.
"Windows 10 Installation, Setup, and Deployment" forum will be migrating to a new home on Microsoft Q&A (Preview)!
We invite you to post new questions in the "Windows 10 Installation, Setup, and Deployment" forum’s new home on Microsoft Q&A (Preview)!
For more information, please refer to the sticky post.


Wednesday, March 18, 2020 7:10 AM

The other 3 partitions are working properly.

If the recovery partition is deleted using third party software (Mini Tool Partition Wizard) how can the recovery partition be recreated?

When performing an in place upgrade repair it will create a new recovery partition when it is done as an upgrade (1903 to 1909)

Would an in place upgrade repair with the same version (1909 > 1909) will it recreate a recovery partition?

If not, what other options are there to recreate the recovery partition?

Also if there is corruption of the recovery partition that is not fixed by chkdsk what other options are there for repair?