HDM17 Advanced v17.20.17 fails to compact MFT on Windows 10 Pro 22H2 system disk c:

[Nick63]

Same error ("Can't move up record 0x..... An invalid parameter was passed to a function") on both variants , with the PC installed application at boot time and with Recover WinPE booted from the flash drive. I have opened tickets to Paragon support but have not received any solutions so far. During this time, the MFT grows and grows because it cannot be truncated. On disks HDD or SSD other than system disk c:, the "Compact MFT" function works OK.

System is Windows 10 Pro 22H2 64-bit OS build 19045.3324 (latest).

Does anyone know a fix for this?

Thank you.

aaaaa.jpg

[Nick63]

UPDATE: The system disk c: is Samsung SSD 970 EVO Plus 500GB NVMe M.2 PCIe. All other drives on my system (where Compact MFT is working), either HDD or SSD, are older generation.

[Nick63]

UPDATE:

Compacting $MFT in virtual mode worked well. In physical mode failed.

hdmengine_stubact.log

>> [Environment]
19.08.2023 19:47:14.292,virtual ,[1676] >> OS version: Microsoft Windows 10 (Version 2004) WindowsPE 64-bit 2004 (Build 19041.1) (WindowsPE)
19.08.2023 19:47:14.292,virtual ,[1676] >>
19.08.2023 19:47:14.292,virtual ,[1676] >> [Operation]
19.08.2023 19:47:14.292,virtual ,[1676] >> Compact $MFT
19.08.2023 19:47:14.292,virtual ,[1676] >> Code: 537 (0x219)
19.08.2023 19:47:14.292,virtual ,[1676] >> Virtual: 1 (0x1)
19.08.2023 19:47:14.292,virtual ,[1676] >>
19.08.2023 19:47:14.292,virtual ,[1676] >> [Source]
19.08.2023 19:47:14.292,virtual ,[1676] >> DiskNumber: 4 (0x4)
19.08.2023 19:47:14.292,virtual ,[1676] >> DiskDynamic: 0 (0x0)
19.08.2023 19:47:14.292,virtual ,[1676] >> DiskRetained: 0 (0x0)
19.08.2023 19:47:14.292,virtual ,[1676] >> DiskVirtual: 0 (0x0)
19.08.2023 19:47:14.292,virtual ,[1676] >> DiskType: Gpt
19.08.2023 19:47:14.292,virtual ,[1676] >> PartitionNumber: 1 (0x1)
19.08.2023 19:47:14.292,virtual ,[1676] >> Primary: 1 (0x1)
19.08.2023 19:47:14.292,virtual ,[1676] >> FSType: NTFS
19.08.2023 19:47:14.292,virtual ,[1676] >> Letter: G
19.08.2023 19:47:14.292,virtual ,[1676] >>
19.08.2023 19:47:14.292,virtual ,[1676] >> [Parameters]
19.08.2023 19:47:14.292,virtual ,[1676] >> Move records to head: 1 (0x1)
19.08.2023 19:47:14.292,virtual ,[1676] >> Truncate MFT: 1 (0x1)
19.08.2023 19:47:14.292,virtual ,[1676] >>
19.08.2023 19:47:14.292,virtual ,[1676] >> [Result]
19.08.2023 19:47:14.292,virtual ,[1676] >> Error: 0 (0x0)
[Environment]
19.08.2023 19:47:14.305,physical,[1676] OS version: Microsoft Windows 10 (Version 2004) WindowsPE 64-bit 2004 (Build 19041.1) (WindowsPE)
19.08.2023 19:47:14.305,physical,[1676]
19.08.2023 19:47:14.305,physical,[1676] [Operation]
19.08.2023 19:47:14.305,physical,[1676] Compact $MFT
19.08.2023 19:47:14.305,physical,[1676] Code: 537 (0x219)
19.08.2023 19:47:14.305,physical,[1676] Virtual: 0 (0x0)
19.08.2023 19:47:14.305,physical,[1676]
19.08.2023 19:47:14.305,physical,[1676] [Source]
19.08.2023 19:47:14.305,physical,[1676] DiskNumber: 4 (0x4)
19.08.2023 19:47:14.305,physical,[1676] DiskDynamic: 0 (0x0)
19.08.2023 19:47:14.305,physical,[1676] DiskRetained: 0 (0x0)
19.08.2023 19:47:14.305,physical,[1676] DiskVirtual: 0 (0x0)
19.08.2023 19:47:14.305,physical,[1676] DiskType: Gpt
19.08.2023 19:47:14.305,physical,[1676] PartitionNumber: 1 (0x1)
19.08.2023 19:47:14.305,physical,[1676] Primary: 1 (0x1)
19.08.2023 19:47:14.305,physical,[1676] FSType: NTFS
19.08.2023 19:47:14.305,physical,[1676] Letter: G
19.08.2023 19:47:14.305,physical,[1676]
19.08.2023 19:47:14.305,physical,[1676] [Parameters]
19.08.2023 19:47:14.305,physical,[1676] Move records to head: 1 (0x1)
19.08.2023 19:47:14.305,physical,[1676] Truncate MFT: 1 (0x1)
19.08.2023 19:47:16.706,physical,[1676]
19.08.2023 19:47:16.706,physical,[1676] [Result]
19.08.2023 19:47:16.706,physical,[1676] Error: 65632 (0x10060)
19.08.2023 19:47:16.706,physical,[1676] An invalid parameter was passed to a function.
19.08.2023 19:47:16.706,physical,[1676] Please try to run OS built-in tools for checking and correcting file system errors.

SSD is in good condition.
SSD_tested_OK.jpg

chkdsk /f /r /x was performed from recovery flash drive (WindowsPE 64-bit 2004 (Build 19041.1) (WindowsPE)), before the "Compact MFT" was tried and failed.
chkdsk.jpg

[Nick63]

If anyone still reads this forum not too crowded, I want to convey my conclusions.

After a series of tests, I came to the conclusion that the Compact MFT function only works RANDOMLY in HDM17 Advanced. There are bugs in the application. Instead with WinPE HDM12 Server (from 2012), Compact MFT always works successfully. True "paragon". Too bad that HDM12 Server WinPE does not see NVMe M.2 drivers and I cannot do Compact MFT on the system disk that is a NVMe driver.

By the other hand, on disks where HDM17 Advanced gives errors when using Compact MFT, everything is OK when I use chkdsk /f /x offline from a flash driver. I hope that this error in HDM17 Advanced will be corrected now with new updates and not to be corrected in a possible future HDM18, so that I pay more money. I feel like I paid good money for a defective product.

[wmo2]

Hi Nick63,

I have very similar problem (system version, paragon version, disk) , after compacting MFT (and trimming) by Paragon and restart (required by Paragon) my Windows 10 worked fine but with the next restart chkdsk started running in the early stage of the starting Windows. Chkdsk performed operations, no errors found, and after that Windows start was to continue but it got stuck with a small wheel of dots rolling at the bottom of the screen.

The windows partition is boot camp on Mac and under Mac I found that the partition is marked dirty. All the files and folder are there on the disk (ntfs tool is on Mac to see it)

I have no idea how to make the windows start - could you please help me with that?
I'd really appreciate