jaclaz Posted February 21 Share Posted February 21 Good now reboot to XP and run CHKDSK on it. Post results. Then reboot to 10 and run it again on 10. Post results. jaclaz Link to comment Share on other sites More sharing options...
Dave-H Posted February 21 Share Posted February 21 OK, here's what i got when I went back to XP. Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. D:\Users\Dave>chkdsk t: The type of the file system is NTFS. Volume label is BACKUP. WARNING! F parameter not specified. Running CHKDSK in read-only mode. CHKDSK is verifying files (stage 1 of 3)... File verification completed. CHKDSK is verifying indexes (stage 2 of 3)... Index verification completed. CHKDSK is verifying security descriptors (stage 3 of 3)... Security descriptor verification completed. Windows has checked the file system and found no problems. 2861586 MB total disk space. 1617508832 KB in 85507 files. 27348 KB in 1716 indexes. 0 KB in bad sectors. 265220 KB in use by the system. 65536 KB occupied by the log file. 1312463684 KB available on disk. 4096 bytes in each allocation unit. 732566271 total allocation units on disk. 328115921 allocation units available on disk. D:\Users\Dave> And here's what I got back in 10. Microsoft Windows [Version 10.0.19045.4046] (c) Microsoft Corporation. All rights reserved. C:\WINDOWS\system32>chkdsk t: The type of the file system is NTFS. Volume label is BACKUP. WARNING! /F parameter not specified. Running CHKDSK in read-only mode. Stage 1: Examining basic file system structure ... Attribute record (80, "") from file record segment 14E0C is corrupt. Attribute record (80, "") from file record segment 14E11 is corrupt. Attribute record (80, "") from file record segment 14E13 is corrupt. Attribute record (80, "") from file record segment 14E18 is corrupt. Attribute record (80, "") from file record segment 14E19 is corrupt. Attribute record (80, "") from file record segment 14E1A is corrupt. Attribute record (80, "") from file record segment 14E1B is corrupt. Attribute record (80, "") from file record segment 14E6B is corrupt. Attribute record (80, "") from file record segment 14E6C is corrupt. Attribute record (80, "") from file record segment 14E70 is corrupt. Attribute record (80, "") from file record segment 14E76 is corrupt. Attribute record (80, "") from file record segment 14E78 is corrupt. Attribute record (80, "") from file record segment 14E7D is corrupt. Attribute record (A0, $I30) from file record segment 14E9E is corrupt. Attribute record (A0, $I30) from file record segment 14EFD is corrupt. Attribute record (A0, $I30) from file record segment 14EFE is corrupt. Attribute record (A0, $I30) from file record segment 14F05 is corrupt. Attribute record (A0, $I30) from file record segment 14F12 is corrupt. Attribute record (A0, $I30) from file record segment 14F21 is corrupt. Attribute record (A0, $I30) from file record segment 14F2E is corrupt. Attribute record (A0, $I30) from file record segment 14F48 is corrupt. Attribute record (A0, $I30) from file record segment 14F4B is corrupt. Attribute record (A0, $I30) from file record segment 15037 is corrupt. Attribute record (A0, $I30) from file record segment 15042 is corrupt. Attribute record (A0, $I30) from file record segment 15048 is corrupt. Attribute record (A0, $I30) from file record segment 1504F is corrupt. Attribute record (A0, $I30) from file record segment 15073 is corrupt. Attribute record (A0, $I30) from file record segment 15074 is corrupt. Attribute record (A0, $I30) from file record segment 15091 is corrupt. Attribute record (A0, $I30) from file record segment 150A8 is corrupt. Attribute record (A0, $I30) from file record segment 150C5 is corrupt. Attribute record (A0, $I30) from file record segment 150CF is corrupt. Attribute record (A0, $I30) from file record segment 150ED is corrupt. Attribute record (A0, $I30) from file record segment 150F5 is corrupt. Attribute record (A0, $I30) from file record segment 15107 is corrupt. Attribute record (A0, $I30) from file record segment 15108 is corrupt. Attribute record (A0, $I30) from file record segment 15134 is corrupt. Attribute record (A0, $I30) from file record segment 15142 is corrupt. Attribute record (A0, $I30) from file record segment 15168 is corrupt. Attribute record (A0, $I30) from file record segment 15199 is corrupt. Attribute record (A0, $I30) from file record segment 151D2 is corrupt. Attribute record (A0, $I30) from file record segment 151D3 is corrupt. Attribute record (A0, $I30) from file record segment 151EC is corrupt. Attribute record (A0, $I30) from file record segment 1521D is corrupt. Attribute record (A0, $I30) from file record segment 15272 is corrupt. Attribute record (A0, $I30) from file record segment 1A3BB is corrupt. Attribute record (A0, $I30) from file record segment 1A407 is corrupt. Attribute record (A0, $I30) from file record segment 1A429 is corrupt. Attribute record (A0, $I30) from file record segment 1A434 is corrupt. Attribute record (A0, $I30) from file record segment 1A435 is corrupt. Attribute record (A0, $I30) from file record segment 1A76D is corrupt. Attribute record (A0, $I30) from file record segment 1A77B is corrupt. Attribute record (80, "") from file record segment 1A781 is corrupt. Attribute record (A0, $I30) from file record segment 1A790 is corrupt. Attribute record (80, "") from file record segment 1A791 is corrupt. Attribute record (A0, $I30) from file record segment 1A7B8 is corrupt. Attribute record (80, "") from file record segment 1A7DD is corrupt. Attribute record (80, "") from file record segment 1A844 is corrupt. Attribute record (80, "") from file record segment 1A855 is corrupt. Attribute record (80, "") from file record segment 1A85F is corrupt. Attribute record (80, "") from file record segment 1A863 is corrupt. Attribute record (80, "") from file record segment 1A864 is corrupt. Attribute record (80, "") from file record segment 1A867 is corrupt. Attribute record (80, "") from file record segment 1A869 is corrupt. Attribute record (80, "") from file record segment 1A870 is corrupt. Attribute record (80, "") from file record segment 1A877 is corrupt. Attribute record (80, "") from file record segment 1A879 is corrupt. Attribute record (80, "") from file record segment 1A87B is corrupt. Attribute record (80, "") from file record segment 1A87E is corrupt. Attribute record (80, "") from file record segment 1A882 is corrupt. Attribute record (80, "") from file record segment 1A889 is corrupt. Attribute record (80, "") from file record segment 1A88A is corrupt. Attribute record (80, "") from file record segment 1A88B is corrupt. Attribute record (80, "") from file record segment 1A88D is corrupt. Attribute record (80, "") from file record segment 1A896 is corrupt. Attribute record (80, "") from file record segment 1A8A4 is corrupt. Attribute record (80, "") from file record segment 1A8A6 is corrupt. Attribute record (80, "") from file record segment 1A8B0 is corrupt. Attribute record (A0, $I30) from file record segment 1AA4C is corrupt. Attribute record (A0, $I30) from file record segment 1AA4D is corrupt. Attribute record (80, "") from file record segment 1AA5E is corrupt. Attribute record (80, "") from file record segment 1AA63 is corrupt. Attribute record (80, "") from file record segment 1AA81 is corrupt. Attribute record (80, "") from file record segment 1AA82 is corrupt. Attribute record (80, "") from file record segment 1AA83 is corrupt. Attribute record (80, "") from file record segment 1AA85 is corrupt. Attribute record (80, "") from file record segment 1AA86 is corrupt. Attribute record (80, "") from file record segment 1AA87 is corrupt. Attribute record (80, "") from file record segment 1AA88 is corrupt. Attribute record (80, "") from file record segment 1AA8A is corrupt. Attribute record (80, "") from file record segment 1AA8B is corrupt. Attribute record (80, "") from file record segment 1AA8C is corrupt. Attribute record (80, "") from file record segment 1AA8D is corrupt. Attribute record (80, "") from file record segment 1AA8E is corrupt. Attribute record (80, "") from file record segment 1AA8F is corrupt. Attribute record (80, "") from file record segment 1AA90 is corrupt. Attribute record (80, "") from file record segment 1AA91 is corrupt. Attribute record (80, "") from file record segment 1AA92 is corrupt. Attribute record (80, "") from file record segment 1AA93 is corrupt. Attribute record (80, "") from file record segment 1AA95 is corrupt. Attribute record (80, "") from file record segment 1AABA is corrupt. Attribute record (80, "") from file record segment 1AABC is corrupt. Attribute record (80, "") from file record segment 1AABE is corrupt. Attribute record (80, "") from file record segment 1AABF is corrupt. Attribute record (80, "") from file record segment 1AAC0 is corrupt. Attribute record (80, "") from file record segment 1AAC1 is corrupt. Attribute record (80, "") from file record segment 1AAC3 is corrupt. Attribute record (80, "") from file record segment 1AAC4 is corrupt. Attribute record (80, "") from file record segment 1AAC5 is corrupt. Attribute record (80, "") from file record segment 1AAC6 is corrupt. Attribute record (80, "") from file record segment 1AAC7 is corrupt. Attribute record (80, "") from file record segment 1AAC8 is corrupt. Attribute record (80, "") from file record segment 1AAC9 is corrupt. Attribute record (80, "") from file record segment 1AACA is corrupt. Attribute record (80, "") from file record segment 1AACB is corrupt. Attribute record (80, "") from file record segment 1AACC is corrupt. Attribute record (80, "") from file record segment 1AACD is corrupt. Attribute record (80, "") from file record segment 1AAD0 is corrupt. Attribute record (80, "") from file record segment 1AAD1 is corrupt. Attribute record (80, "") from file record segment 1AAD2 is corrupt. Attribute record (80, "") from file record segment 1AAD3 is corrupt. Attribute record (80, "") from file record segment 1AAD4 is corrupt. Attribute record (80, "") from file record segment 1AAD5 is corrupt. Attribute record (80, "") from file record segment 1AAD7 is corrupt. Attribute record (80, "") from file record segment 1AAD8 is corrupt. Attribute record (80, "") from file record segment 1AAD9 is corrupt. Attribute record (80, "") from file record segment 1AADA is corrupt. Attribute record (80, "") from file record segment 1AADB is corrupt. Attribute record (80, "") from file record segment 1AADC is corrupt. Attribute record (80, "") from file record segment 1AADD is corrupt. Attribute record (80, "") from file record segment 1AADE is corrupt. Attribute record (80, "") from file record segment 1AAE0 is corrupt. Attribute record (80, "") from file record segment 1AAE1 is corrupt. Attribute record (80, "") from file record segment 1AAE2 is corrupt. Attribute record (80, "") from file record segment 1AAE3 is corrupt. Attribute record (80, "") from file record segment 1AAE4 is corrupt. Attribute record (80, "") from file record segment 1AAE5 is corrupt. Attribute record (80, "") from file record segment 1AAE6 is corrupt. Attribute record (80, "") from file record segment 1AAE7 is corrupt. Attribute record (80, "") from file record segment 1AAE8 is corrupt. Attribute record (80, "") from file record segment 1AAE9 is corrupt. Attribute record (80, "") from file record segment 1AAEA is corrupt. Attribute record (80, "") from file record segment 1AAEB is corrupt. Attribute record (80, "") from file record segment 1AAEC is corrupt. Attribute record (80, "") from file record segment 1AAED is corrupt. Attribute record (80, "") from file record segment 1AAEE is corrupt. Attribute record (80, "") from file record segment 1AAEF is corrupt. Attribute record (80, "") from file record segment 1AAF0 is corrupt. Attribute record (80, "") from file record segment 1AAF1 is corrupt. Attribute record (80, "") from file record segment 1AAF2 is corrupt. Attribute record (80, "") from file record segment 1AAF3 is corrupt. Attribute record (80, "") from file record segment 1AAF4 is corrupt. Attribute record (80, "") from file record segment 1AAF5 is corrupt. Attribute record (80, "") from file record segment 1AAF6 is corrupt. Attribute record (80, "") from file record segment 1AAF7 is corrupt. Attribute record (80, "") from file record segment 1AAF8 is corrupt. Attribute record (80, "") from file record segment 1AAF9 is corrupt. Attribute record (80, "") from file record segment 1AAFA is corrupt. Attribute record (80, "") from file record segment 1AAFB is corrupt. Attribute record (80, "") from file record segment 1AAFC is corrupt. Attribute record (80, "") from file record segment 1AAFD is corrupt. Attribute record (80, "") from file record segment 1AAFE is corrupt. Attribute record (80, "") from file record segment 1AAFF is corrupt. Attribute record (80, "") from file record segment 1AB00 is corrupt. Attribute record (80, "") from file record segment 1AB01 is corrupt. Attribute record (80, "") from file record segment 1AB02 is corrupt. Attribute record (80, "") from file record segment 1AB03 is corrupt. Attribute record (80, "") from file record segment 1AB04 is corrupt. Attribute record (80, "") from file record segment 1AB05 is corrupt. Attribute record (80, "") from file record segment 1AB06 is corrupt. Attribute record (80, "") from file record segment 1AB07 is corrupt. Attribute record (80, "") from file record segment 1AB08 is corrupt. Attribute record (80, "") from file record segment 1AB09 is corrupt. Attribute record (80, "") from file record segment 1AB0A is corrupt. Attribute record (80, "") from file record segment 1AB0B is corrupt. Attribute record (80, "") from file record segment 1AB0C is corrupt. Attribute record (80, "") from file record segment 1AB0D is corrupt. Attribute record (80, "") from file record segment 1AB0E is corrupt. Attribute record (80, "") from file record segment 1AB0F is corrupt. Attribute record (80, "") from file record segment 1AB10 is corrupt. Attribute record (80, "") from file record segment 1AB11 is corrupt. Attribute record (80, "") from file record segment 1AB12 is corrupt. Attribute record (80, "") from file record segment 1AB13 is corrupt. Attribute record (80, "") from file record segment 1AB14 is corrupt. Attribute record (80, "") from file record segment 1AB15 is corrupt. Attribute record (80, "") from file record segment 1AB16 is corrupt. Attribute record (80, "") from file record segment 1AB17 is corrupt. Attribute record (80, "") from file record segment 1AB18 is corrupt. Attribute record (80, "") from file record segment 1AB19 is corrupt. Attribute record (80, "") from file record segment 1AB1A is corrupt. Attribute record (80, "") from file record segment 1AB1B is corrupt. Attribute record (80, "") from file record segment 1AB1C is corrupt. Attribute record (80, "") from file record segment 1AB1D is corrupt. Attribute record (80, "") from file record segment 1AB1E is corrupt. Attribute record (80, "") from file record segment 1AB1F is corrupt. Attribute record (80, "") from file record segment 1AB20 is corrupt. Attribute record (80, "") from file record segment 1AB21 is corrupt. Attribute record (80, "") from file record segment 1AB22 is corrupt. Attribute record (80, "") from file record segment 1AB23 is corrupt. Attribute record (80, "") from file record segment 1AB24 is corrupt. Attribute record (80, "") from file record segment 1AB25 is corrupt. Attribute record (80, "") from file record segment 1AB26 is corrupt. Attribute record (80, "") from file record segment 1AB40 is corrupt. Attribute record (80, "") from file record segment 1AB41 is corrupt. Attribute record (80, "") from file record segment 1AB42 is corrupt. Attribute record (80, "") from file record segment 1AB49 is corrupt. Attribute record (80, "") from file record segment 1AB64 is corrupt. Attribute record (80, "") from file record segment 1AB90 is corrupt. Attribute record (80, "") from file record segment 1AB9D is corrupt. Attribute record (80, "") from file record segment 1ABCB is corrupt. Attribute record (80, "") from file record segment 1ABCD is corrupt. Attribute record (80, "") from file record segment 1ABD2 is corrupt. Attribute record (80, "") from file record segment 1AC15 is corrupt. Attribute record (80, "") from file record segment 1ACAD is corrupt. Attribute record (80, "") from file record segment 1ACAF is corrupt. Attribute record (80, "") from file record segment 1ACBA is corrupt. 109824 file records processed. File verification completed. Phase duration (File record verification): 7.90 seconds. 2 large file records processed. Phase duration (Orphan file record recovery): 0.00 milliseconds. Errors found. CHKDSK cannot continue in read-only mode. C:\WINDOWS\system32> Looking at the Chkdsk logs it does strike me that the folders with the errors always seem to be the same ones. They are part of my mobile phone backup, mainly image files in folders at at - T:\Phone Backup\Backup\SM-G935F\SM-G935F_07762200581\SM-G935F_20240201191121\Photo\_EXTERNAL_\Archive Whether this is signifiant I don't know, perhaps the path length? Sorry I have to leave this for a few hours now. I'll be back! 2 Link to comment Share on other sites More sharing options...
Dave-H Posted February 21 Share Posted February 21 Thanks to @Andalu I can now hopefully dispense with the Paragon GPT driver. I will do that and see if it makes any difference to the filesystem corruption issue. 1 Link to comment Share on other sites More sharing options...
Dave-H Posted February 23 Share Posted February 23 @Andalu @jaclaz OK, back again! Quite a lot to report. Thanks to @Andalu I have now got rid of the paragon GPT driver. I'm amazed that you can add GPT support to XP just by substituting a few files from its server equivalent, but I'm not complaining! A much more elegant way of doing it, even though I gather that I can now no longer connect the disk directly to the motherboard, I have to use the Asmedia card. Anyway, that is all working fine, but it didn't get rid of the file system errors. I then analysed what was happening more closely, and I realised that all the files which were showing errors in chkdsk were files that had been added to the drive in the last few weeks. There are many thousands of other older files in the drive which appear to be always absolutely fine. So, it is just possible that this file system corruption is in fact nothing to do with the way the disk is connected in XP, or what driver it may or may not be using. I analysed which files were always appearing in the error messages, and folder by folder, I deleted them from the drive. The error lists gradually got shorter and shorter. It took me a long time to get rid of some of them permanently, as running chkdsk on the other OS sometimes put them back again! Some were actually stuck (invisibly) in the Recycle Bin, and it was a bit of a job getting rid of them! I now have clean chkdsk runs on both XP and 10, which is a great relief! Now I'm wondering what I can do to minimise the chance of the problem coming back again as soon as I do another backup, particularly which OS is safest to do it in. I use a program called QuickMirror to do my file backups. I've been using it for many years, and it's never caused any problem. It's really fast, as the name implies! Until recently I've only ever used it on Windows XP and Windows 98, but recently they produced an update which initially didn't work on XP or 98, so I installed it on 10. I did several backups with it, with apparently no problems, until the issue was fixed on XP and I could use it there. I assumed I could have (separate) copies of it on XP and 10, and use whichever I liked. Maybe this was a mistake! I've been doing backups using both operating systems, and I think that's when the problems started, in fact the first symptoms were when I started to get errors during the backup process. I've no reason to think that QuickMirror does anything differently on XP and 10, so this is a bit of a puzzle. I will certainly be on to the developer immediately if I find that this is indeed the case! Any thoughts? Link to comment Share on other sites More sharing options...
jaclaz Posted February 23 Share Posted February 23 I am also not convinced that the errors you got come from the added SATA card, the riser or some other combination of hardware /drivers. They seem to me too "specific" to be attributed to hardware issues. I have seen similar reports by people that were accessing NTFS with this (or that) version of filesystem drivers from Linux, related (directly or indirectly) to short name generation, but XP and 10 should not produce errors for this reason, other similar errors have been reported involving "NTFS resident" data, files smaller than around 780 bytes, but your files are "normal" ones. The paths you have shared are long, but not long enough to hit this (or that) limitation (that I know of), 102 characters for the path + an even longish filename won't ever touch the 255 character limit. And I don't think that the Paragon GPT driver is involved either, it should work at a "lower" level giving access to the volume, so from then on it is (NTFS) filesystem drivers that are in control. On the other hand the backup tool you have, if it uses some kind of caching/flow control or similar may (evidently in extremely rare cases) produce some kind of race condition that leads to the errors. BUT it is still not too convincing as a thesis, as - once the mis-writes of the relevant bytes happened - the error should be detected by BOTH the Windows 10 AND the XP CHKDSK. So, if it is detected on only one of the two OS, and this behaviour is consistent, it should mean that XP *somehow* writes differently from Windows 10 (and Windows 10 doesn't *like* the way XP writes in NTFS) which makes very little sense, as we would have seen tens, hundreds or thousands of similar error reports. I am really perplexed. Link to comment Share on other sites More sharing options...
Dave-H Posted February 23 Share Posted February 23 You and me both! QuickMirror does use caching and multithreading when doing its backups, depending on the operating system, but whether that is relevant I don't know. If you haven't looked already, you can see the details at QuickMirror.com. There were a couple of files with errors that I know were not copied to the drive by QuickMirror, but the vast majority were, and all since the beginning of this month. Link to comment Share on other sites More sharing options...
jaclaz Posted February 23 Share Posted February 23 4 minutes ago, Dave-H said: There were a couple of files with errors that I know were not copied to the drive by QuickMirror, but the vast majority were, and all since the beginning of this month. Yep, but that is only due to February having 29 days this year. jaclaz 1 Link to comment Share on other sites More sharing options...
Dixel Posted February 23 Share Posted February 23 "ObviouslyI have my suspicion that this drive is faulty, which is strange because it isn't very old. maybe 1-2yrs maximum. " "So before I attempted to do anything in disk management, I opened up minitool partition wizard and tried to recover "lost partition" with no success. I then tried minitool power data recovery programme..." "csharpe1234, is your issue resolved? I am facing the same issue." "I had to accept that the drive was faulty and unrecoverable. I bought a new drive." https://forums.tomshardware.com/threads/seagate-barracuda-st3000dm001-3tb-sata-not-recognised-in-bios-or-disk-management.1670124/ 2 Link to comment Share on other sites More sharing options...
jaclaz Posted February 23 Share Posted February 23 From experience, whenever someone posts "I am facing the same issue" it means that it is a different one, with a confidence level of 99.99%. This said, something completely different was reported to happen some 8-9 years ago to a poor chap. We have got by now the idea that that particular model of Seagate drive is prone to failure (particularly if run 24h/7 in a data center), but the one Dave-H has shows none of the signs of a failing drive, so, while it may fail tomorrow, it hasn't yet. jaclaz 1 Link to comment Share on other sites More sharing options...
Dixel Posted February 23 Share Posted February 23 4 hours ago, jaclaz said: This said, something completely different was reported to happen some 8-9 years ago to a poor chap. We have got by now the idea that that particular model of Seagate drive is prone to failure (particularly if run 24h/7 in a data center), but the one Dave-H has shows none of the signs of a failing drive, so, while it may fail tomorrow, it hasn't yet. jaclaz I was in the same shoes with that poor chap, soon after 1 year of warranty ended, files started to disappear, big files started to lose parts, like an mp4 video 8Gb in size. HDD sentinel didn't pick any signs of failing at all. I think most of us had encounters with that drive, I only had 2 of them, both in that infamous Apple boxes, both behaved weirdly and failed soon after. And no, it's not a server model, not suitable for a data centre. It's a very basic disk, consumer grade model. 4 Link to comment Share on other sites More sharing options...
Dave-H Posted February 23 Share Posted February 23 OK, I tried today doing another ISO backup of my Windows 10 system drive, using Windows 7 Backup and Restore (yes, I know, I know!) which I usually do every week. It went fine, and there were no errors in chkdsk after it. I then went into Windows XP, and checked with chkdsk again, still no issues recorded except for one, "Correcting errors in the uppercase file." I think that's fairly minor. So far, so good. @Andalu One issue that has now come up on XP is that the drive is fine if I power up the enclosure before booting to XP. However, if I power it up while I'm in XP, where it should just appear as it's on an eSATA connection, I get this - If I say 'Continue Anyway' I then get this - Obviously I say 'no' as I don't want to overwrite the Win2003 DISK.SYS file! The drive then installs. This seems to happen every time I try to add the disk while I'm in XP. Is this normal expected behaviour? If it is, it's rather a PITA! Can anything be done to avoid it? I would perhaps have expected something like this the first time I did, but not every time. Why doesn't it remember the disk? Link to comment Share on other sites More sharing options...
Andalu Posted February 23 Share Posted February 23 (edited) @Dave-H it depends from the System File Checker which attempts to restore the original versions of the system files. If you do not want to completely disable that SFC\WFP function, try copying disk.sys v5.2.3790.4006 to the windows\system32\dllcache folder, in the hope that this will be enough to prevent that procedure from occurring every time the disk is connected to the system. Otherwise, you also need to disable SFC/WFP. Edit: I don't want to repeat the same thing over and over again, but it's worth mentioning that I still haven't been able to figure out why the problem I reported here occurred. Therefore, if you have the chance, make your backups in another location as well, to avoid a loss of data in case this problem occurs for you also. Edited February 23 by Andalu Link to comment Share on other sites More sharing options...
Dave-H Posted February 23 Share Posted February 23 Thanks, I did wonder if SFC and/or Windows File Protection was causing the problem. There is no record of this in the system event logs though, and I thought there usually is if WFP restores, or tries to restore, a file. I had already copied the 'new' disk.sys file to DLLCache, and scsiport.sys too. Neither of them were there at all previously. partmgr.sys was already in the DLLCache folder, and I replaced it with the 'new' one too. The strange thing is, that file replace message refers to a temporary file. When I looked at the temporary file, its version details said it was actually the original version of scsidisk.sys, not disk.sys! I can't explain that, except that perhaps it's renamed to disk.sys when it's copied. Link to comment Share on other sites More sharing options...
mina7601 Posted February 23 Share Posted February 23 2 hours ago, Andalu said: Otherwise, you also need to disable SFC/WFP. Or you could just use Replacer, an alternative way of replacing system files without disabling Windows File Protection. Link to comment Share on other sites More sharing options...
dmiranda Posted February 23 Share Posted February 23 I don't see a real use for SFC/WFP since forever. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now