imagex image/sfc

I used imagex to make a Windows image.  I transferred it to a spare drive to make sure it worked.  It did.

Next, I transferred it to the real target drive (a larger drive).  I happened to do a system file check to make sure everything was okay.  It said it found corrupt files, but could not fix them.  I went back and also checked the practice drive but found no problems.

I searched the cbs log for "corrupt", but none found.  If I upload the cbs log, could someone look at it and let me know what is happening?

Thank-you.

Hi ray5450:

Your CBS.log might be larger than the maximum file size users are allowed to upload in this forum.

I'm probably not qualified to interpret the results of your System File Checker (SFC) scan log, but every entry in the CBS.log file created by sfc.exe has a [SR] tag.  If you have a Vista SP2 computer, follow the instructions in the MS support article How to analyze the log file entries that the Microsoft Windows Resource Checker (SFC.exe) program generates in Windows Vista to export your SFC scan log to a smaller text file. 

As noted in those instructions, if you open an elevated command prompt (with Administrator rights) and type in the command findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >C:\sfcdetails.txt your SFC scan log will be saved in a text file called sfcdetails.txt in your root C:\ directory.

-----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.4.0 * NS Premium v22.11.0.41 * MB Premium v3.3.1
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS

Okay, I made the file and it was not very big.  I looked through it and there were no occurrences of "corrupt" or "cannot".  Why then, is it saying after the scan that there are corrupt files that cannot be repaired?

Thanks.

Hi ray5450:

Could you please attach the text file of the SFC scan log you extracted from CBS.log to your next post?

I use Macrium Reflect Free so hopefully someone more familiar with ImageX will post in this thread and let you know if this program has the ability to dynamically adjust the partition size when you apply an image to a target drive that's larger than the source drive.  Here are a few suggestions while you're waiting for help, though:

Run a thorough Check Disk (i.e., run the command chkdsk /r from an elevated command prompt and re-boot to start the scheduled scan as described in the tutorial <here>) to look for and repair any bad sectors on the new hard drive.  The Ask Leo! article How do I see the results of a CHKDSK that ran on boot? shows how to find the ChkDsk results in your Windows Event Viewer - look for an event with the Source listed as Wininit.

It would also be helpful if you ran a quick diagnostic with Piriform's free Speccy and then published a snapshot of your system specs on the web (File | Publish Snapshot) .  Follow the instructions in the support article Publishing a Speccy Profile to the Web and then copy and paste the URL of your published snapshot in your next post..  If you don't want to install Speccy on your hard drive, Piriform also offers a portable version on their builds page at http://www.piriform.com/speccy/builds that you can unzip and run from a USB thumb drive.  Here's the URL of a sample snapshot I created today for my own Vista SP2 computer:

         http://speccy.piriform.com/results/UG7Gav8TNx5Pm0RzoERIjLr

There's an older ImageX tutorial on the ITPro site titled Deploying and Error Checking with ImageX that might also help.  Did you use the /check switch when you were capturing the image of your old hard drive, and use the /check or /verfiy switches when applying your image to the new hard drive?
-----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.4.0 * NS Premium v22.11.0.41 * MB Premium v3.3.1
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS

Edited by lmacri, 06 November 2017 - 06:38 PM.

Yes, I forgot to say that I also did a chkdsk, but no problems.

I did use both /check and /verify.

It appears that the message returned from the sfc command is saying that there are corrupt files, but the log file does not show that.  Except for this discrepancy, I have had no problems with this image...until....I tried to use Speccy.  I have used Speccy many times on this site and did not experience this behavior--right after the information appears in Speccy, the hard drive read/write light goes on and the mouse becomes unresponsive.  The machine is not completely frozen because the light goes off once in awhile for a second, the clock keeps correct, and the screen goes off from the power options and comes back on with a key press.  However, I cannot do anything else.  I let it run for 30 minutes with no change, then did another chkdsk and found no problems, and next tried again and left it all night with no change.  Next, I tried it in safe mode and no difference.  Any ideas on that?

Here is the sfc info:

2017-11-05 21:12:59, Info                  CSI    00000006 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:12:59, Info                  CSI    00000007 [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:09, Info                  CSI    00000009 [SR] Verify complete
2017-11-05 21:13:11, Info                  CSI    0000000a [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:11, Info                  CSI    0000000b [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:18, Info                  CSI    0000000d [SR] Verify complete
2017-11-05 21:13:19, Info                  CSI    0000000e [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:19, Info                  CSI    0000000f [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:19, Info                  CSI    00000011 [SR] Verify complete
2017-11-05 21:13:22, Info                  CSI    00000012 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:22, Info                  CSI    00000013 [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:23, Info                  CSI    00000015 [SR] Verify complete
2017-11-05 21:13:25, Info                  CSI    00000016 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:25, Info                  CSI    00000017 [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:27, Info                  CSI    00000019 [SR] Verify complete
2017-11-05 21:13:35, Info                  CSI    0000001a [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:35, Info                  CSI    0000001b [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:36, Info                  CSI    0000001d [SR] Verify complete
2017-11-05 21:13:36, Info                  CSI    0000001e [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:36, Info                  CSI    0000001f [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:36, Info                  CSI    00000021 [SR] Verify complete
2017-11-05 21:13:37, Info                  CSI    00000022 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:37, Info                  CSI    00000023 [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:38, Info                  CSI    00000025 [SR] Verify complete
2017-11-05 21:13:38, Info                  CSI    00000026 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:38, Info                  CSI    00000027 [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:38, Info                  CSI    00000029 [SR] Verify complete
2017-11-05 21:13:39, Info                  CSI    0000002a [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:39, Info                  CSI    0000002b [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:39, Info                  CSI    0000002d [SR] Verify complete
2017-11-05 21:13:40, Info                  CSI    0000002e [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:40, Info                  CSI    0000002f [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:40, Info                  CSI    00000031 [SR] Verify complete
2017-11-05 21:13:41, Info                  CSI    00000032 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:41, Info                  CSI    00000033 [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:42, Info                  CSI    00000035 [SR] Verify complete
2017-11-05 21:13:44, Info                  CSI    00000036 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:44, Info                  CSI    00000037 [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:44, Info                  CSI    00000039 [SR] Verify complete
2017-11-05 21:13:45, Info                  CSI    0000003a [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:45, Info                  CSI    0000003b [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:47, Info                  CSI    0000003d [SR] Verify complete
2017-11-05 21:13:47, Info                  CSI    0000003e [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:47, Info                  CSI    0000003f [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:48, Info                  CSI    00000041 [SR] Verify complete
2017-11-05 21:13:51, Info                  CSI    00000042 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:51, Info                  CSI    00000043 [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:52, Info                  CSI    00000045 [SR] Verify complete
2017-11-05 21:13:52, Info                  CSI    00000046 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:52, Info                  CSI    00000047 [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:53, Info                  CSI    00000049 [SR] Verify complete
2017-11-05 21:13:54, Info                  CSI    0000004a [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:54, Info                  CSI    0000004b [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:57, Info                  CSI    0000004d [SR] Verify complete
2017-11-05 21:13:58, Info                  CSI    0000004e [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:58, Info                  CSI    0000004f [SR] Beginning Verify and Repair transaction
2017-11-05 21:13:58, Info                  CSI    00000051 [SR] Verify complete
2017-11-05 21:13:59, Info                  CSI    00000052 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:13:59, Info                  CSI    00000053 [SR] Beginning Verify and Repair transaction
2017-11-05 21:14:01, Info                  CSI    00000055 [SR] Verify complete
2017-11-05 21:14:02, Info                  CSI    00000056 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:14:02, Info                  CSI    00000057 [SR] Beginning Verify and Repair transaction
2017-11-05 21:14:02, Info                  CSI    00000059 [SR] Verify complete
2017-11-05 21:14:03, Info                  CSI    0000005a [SR] Verifying 100 (0x00000064) components
2017-11-05 21:14:03, Info                  CSI    0000005b [SR] Beginning Verify and Repair transaction
2017-11-05 21:14:04, Info                  CSI    0000005d [SR] Verify complete
2017-11-05 21:14:04, Info                  CSI    0000005e [SR] Verifying 100 (0x00000064) components
2017-11-05 21:14:04, Info                  CSI    0000005f [SR] Beginning Verify and Repair transaction
2017-11-05 21:14:05, Info                  CSI    00000061 [SR] Verify complete
2017-11-05 21:14:05, Info                  CSI    00000062 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:14:05, Info                  CSI    00000063 [SR] Beginning Verify and Repair transaction
2017-11-05 21:14:07, Info                  CSI    00000065 [SR] Verify complete
2017-11-05 21:14:08, Info                  CSI    00000066 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:14:08, Info                  CSI    00000067 [SR] Beginning Verify and Repair transaction
2017-11-05 21:14:09, Info                  CSI    00000069 [SR] Verify complete
2017-11-05 21:14:10, Info                  CSI    0000006a [SR] Verifying 100 (0x00000064) components
2017-11-05 21:14:10, Info                  CSI    0000006b [SR] Beginning Verify and Repair transaction
2017-11-05 21:14:11, Info                  CSI    0000006d [SR] Verify complete
2017-11-05 21:14:12, Info                  CSI    0000006e [SR] Verifying 100 (0x00000064) components
2017-11-05 21:14:12, Info                  CSI    0000006f [SR] Beginning Verify and Repair transaction
2017-11-05 21:14:16, Info                  CSI    00000071 [SR] Verify complete
2017-11-05 21:14:17, Info                  CSI    00000072 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:14:17, Info                  CSI    00000073 [SR] Beginning Verify and Repair transaction
2017-11-05 21:14:26, Info                  CSI    00000075 [SR] Verify complete
2017-11-05 21:14:28, Info                  CSI    00000076 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:14:28, Info                  CSI    00000077 [SR] Beginning Verify and Repair transaction
2017-11-05 21:14:33, Info                  CSI    00000079 [SR] Verify complete
2017-11-05 21:14:35, Info                  CSI    0000007a [SR] Verifying 100 (0x00000064) components
2017-11-05 21:14:35, Info                  CSI    0000007b [SR] Beginning Verify and Repair transaction
2017-11-05 21:14:41, Info                  CSI    0000007e [SR] Verify complete
2017-11-05 21:14:42, Info                  CSI    0000007f [SR] Verifying 100 (0x00000064) components
2017-11-05 21:14:42, Info                  CSI    00000080 [SR] Beginning Verify and Repair transaction
2017-11-05 21:14:49, Info                  CSI    00000083 [SR] Verify complete
2017-11-05 21:14:51, Info                  CSI    00000084 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:14:51, Info                  CSI    00000085 [SR] Beginning Verify and Repair transaction
2017-11-05 21:15:02, Info                  CSI    00000087 [SR] Verify complete
2017-11-05 21:15:06, Info                  CSI    00000088 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:15:06, Info                  CSI    00000089 [SR] Beginning Verify and Repair transaction
2017-11-05 21:15:30, Info                  CSI    00000093 [SR] Verify complete
2017-11-05 21:15:31, Info                  CSI    00000094 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:15:31, Info                  CSI    00000095 [SR] Beginning Verify and Repair transaction
2017-11-05 21:15:43, Info                  CSI    00000097 [SR] Verify complete
2017-11-05 21:15:44, Info                  CSI    00000098 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:15:44, Info                  CSI    00000099 [SR] Beginning Verify and Repair transaction
2017-11-05 21:15:57, Info                  CSI    0000009b [SR] Verify complete
2017-11-05 21:15:59, Info                  CSI    0000009c [SR] Verifying 100 (0x00000064) components
2017-11-05 21:15:59, Info                  CSI    0000009d [SR] Beginning Verify and Repair transaction
2017-11-05 21:16:20, Info                  CSI    0000009f [SR] Verify complete
2017-11-05 21:16:25, Info                  CSI    000000a0 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:16:25, Info                  CSI    000000a1 [SR] Beginning Verify and Repair transaction
2017-11-05 21:16:40, Info                  CSI    000000a3 [SR] Verify complete
2017-11-05 21:16:42, Info                  CSI    000000a4 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:16:42, Info                  CSI    000000a5 [SR] Beginning Verify and Repair transaction
2017-11-05 21:17:41, Info                  CSI    000000a9 [SR] Verify complete
2017-11-05 21:17:52, Info                  CSI    000000aa [SR] Verifying 100 (0x00000064) components
2017-11-05 21:17:52, Info                  CSI    000000ab [SR] Beginning Verify and Repair transaction
2017-11-05 21:18:17, Info                  CSI    000000ad [SR] Verify complete
2017-11-05 21:18:18, Info                  CSI    000000ae [SR] Verifying 100 (0x00000064) components
2017-11-05 21:18:18, Info                  CSI    000000af [SR] Beginning Verify and Repair transaction
2017-11-05 21:18:39, Info                  CSI    000000b1 [SR] Verify complete
2017-11-05 21:18:40, Info                  CSI    000000b2 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:18:40, Info                  CSI    000000b3 [SR] Beginning Verify and Repair transaction
2017-11-05 21:18:46, Info                  CSI    000000b5 [SR] Verify complete
2017-11-05 21:18:47, Info                  CSI    000000b6 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:18:47, Info                  CSI    000000b7 [SR] Beginning Verify and Repair transaction
2017-11-05 21:18:50, Info                  CSI    000000b9 [SR] Verify complete
2017-11-05 21:18:50, Info                  CSI    000000ba [SR] Verifying 100 (0x00000064) components
2017-11-05 21:18:50, Info                  CSI    000000bb [SR] Beginning Verify and Repair transaction
2017-11-05 21:19:02, Info                  CSI    000000c7 [SR] Verify complete
2017-11-05 21:19:03, Info                  CSI    000000c8 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:19:03, Info                  CSI    000000c9 [SR] Beginning Verify and Repair transaction
2017-11-05 21:19:22, Info                  CSI    000000dd [SR] Verify complete
2017-11-05 21:19:23, Info                  CSI    000000de [SR] Verifying 100 (0x00000064) components
2017-11-05 21:19:23, Info                  CSI    000000df [SR] Beginning Verify and Repair transaction
2017-11-05 21:19:24, Info                  CSI    000000e1 [SR] Verify complete
2017-11-05 21:19:25, Info                  CSI    000000e2 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:19:25, Info                  CSI    000000e3 [SR] Beginning Verify and Repair transaction
2017-11-05 21:19:31, Info                  CSI    000000e5 [SR] Verify complete
2017-11-05 21:19:32, Info                  CSI    000000e6 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:19:32, Info                  CSI    000000e7 [SR] Beginning Verify and Repair transaction
2017-11-05 21:19:41, Info                  CSI    000000e9 [SR] Verify complete
2017-11-05 21:19:43, Info                  CSI    000000ea [SR] Verifying 100 (0x00000064) components
2017-11-05 21:19:43, Info                  CSI    000000eb [SR] Beginning Verify and Repair transaction
2017-11-05 21:19:59, Info                  CSI    000000ed [SR] Verify complete
2017-11-05 21:20:01, Info                  CSI    000000ee [SR] Verifying 100 (0x00000064) components
2017-11-05 21:20:01, Info                  CSI    000000ef [SR] Beginning Verify and Repair transaction
2017-11-05 21:20:05, Info                  CSI    000000f1 [SR] Verify complete
2017-11-05 21:20:06, Info                  CSI    000000f2 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:20:06, Info                  CSI    000000f3 [SR] Beginning Verify and Repair transaction
2017-11-05 21:20:15, Info                  CSI    000000f5 [SR] Verify complete
2017-11-05 21:20:22, Info                  CSI    000000f6 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:20:22, Info                  CSI    000000f7 [SR] Beginning Verify and Repair transaction
2017-11-05 21:20:29, Info                  CSI    000000f9 [SR] Verify complete
2017-11-05 21:20:32, Info                  CSI    000000fa [SR] Verifying 100 (0x00000064) components
2017-11-05 21:20:32, Info                  CSI    000000fb [SR] Beginning Verify and Repair transaction
2017-11-05 21:20:41, Info                  CSI    000000fd [SR] Verify complete
2017-11-05 21:20:44, Info                  CSI    000000fe [SR] Verifying 100 (0x00000064) components
2017-11-05 21:20:44, Info                  CSI    000000ff [SR] Beginning Verify and Repair transaction
2017-11-05 21:21:10, Info                  CSI    00000112 [SR] Verify complete
2017-11-05 21:21:10, Info                  CSI    00000113 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:21:10, Info                  CSI    00000114 [SR] Beginning Verify and Repair transaction
2017-11-05 21:21:34, Info                  CSI    00000128 [SR] Verify complete
2017-11-05 21:21:39, Info                  CSI    00000129 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:21:39, Info                  CSI    0000012a [SR] Beginning Verify and Repair transaction
2017-11-05 21:22:23, Info                  CSI    0000012c [SR] Verify complete
2017-11-05 21:22:23, Info                  CSI    0000012d [SR] Verifying 100 (0x00000064) components
2017-11-05 21:22:23, Info                  CSI    0000012e [SR] Beginning Verify and Repair transaction
2017-11-05 21:22:51, Info                  CSI    00000130 [SR] Verify complete
2017-11-05 21:22:51, Info                  CSI    00000131 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:22:51, Info                  CSI    00000132 [SR] Beginning Verify and Repair transaction
2017-11-05 21:23:10, Info                  CSI    00000134 [SR] Verify complete
2017-11-05 21:23:10, Info                  CSI    00000135 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:23:10, Info                  CSI    00000136 [SR] Beginning Verify and Repair transaction
2017-11-05 21:23:22, Info                  CSI    00000138 [SR] Verify complete
2017-11-05 21:23:23, Info                  CSI    00000139 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:23:23, Info                  CSI    0000013a [SR] Beginning Verify and Repair transaction
2017-11-05 21:23:30, Info                  CSI    0000013c [SR] Verify complete
2017-11-05 21:23:31, Info                  CSI    0000013d [SR] Verifying 100 (0x00000064) components
2017-11-05 21:23:31, Info                  CSI    0000013e [SR] Beginning Verify and Repair transaction
2017-11-05 21:23:37, Info                  CSI    00000141 [SR] Verify complete
2017-11-05 21:23:38, Info                  CSI    00000142 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:23:38, Info                  CSI    00000143 [SR] Beginning Verify and Repair transaction
2017-11-05 21:23:53, Info                  CSI    00000145 [SR] Verify complete
2017-11-05 21:23:54, Info                  CSI    00000146 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:23:54, Info                  CSI    00000147 [SR] Beginning Verify and Repair transaction
2017-11-05 21:24:02, Info                  CSI    00000149 [SR] Verify complete
2017-11-05 21:24:03, Info                  CSI    0000014a [SR] Verifying 100 (0x00000064) components
2017-11-05 21:24:03, Info                  CSI    0000014b [SR] Beginning Verify and Repair transaction
2017-11-05 21:24:10, Info                  CSI    0000014d [SR] Verify complete
2017-11-05 21:24:11, Info                  CSI    0000014e [SR] Verifying 100 (0x00000064) components
2017-11-05 21:24:11, Info                  CSI    0000014f [SR] Beginning Verify and Repair transaction
2017-11-05 21:24:31, Info                  CSI    00000151 [SR] Verify complete
2017-11-05 21:24:32, Info                  CSI    00000152 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:24:32, Info                  CSI    00000153 [SR] Beginning Verify and Repair transaction
2017-11-05 21:24:43, Info                  CSI    00000155 [SR] Verify complete
2017-11-05 21:24:43, Info                  CSI    00000156 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:24:43, Info                  CSI    00000157 [SR] Beginning Verify and Repair transaction
2017-11-05 21:24:50, Info                  CSI    0000015a [SR] Verify complete
2017-11-05 21:24:52, Info                  CSI    0000015b [SR] Verifying 100 (0x00000064) components
2017-11-05 21:24:52, Info                  CSI    0000015c [SR] Beginning Verify and Repair transaction
2017-11-05 21:25:03, Info                  CSI    0000015e [SR] Verify complete
2017-11-05 21:25:05, Info                  CSI    0000015f [SR] Verifying 100 (0x00000064) components
2017-11-05 21:25:05, Info                  CSI    00000160 [SR] Beginning Verify and Repair transaction
2017-11-05 21:25:13, Info                  CSI    00000162 [SR] Verify complete
2017-11-05 21:25:16, Info                  CSI    00000163 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:25:16, Info                  CSI    00000164 [SR] Beginning Verify and Repair transaction
2017-11-05 21:25:32, Info                  CSI    00000166 [SR] Verify complete
2017-11-05 21:25:33, Info                  CSI    00000167 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:25:33, Info                  CSI    00000168 [SR] Beginning Verify and Repair transaction
2017-11-05 21:25:59, Info                  CSI    0000016d [SR] Verify complete
2017-11-05 21:26:04, Info                  CSI    0000016e [SR] Verifying 100 (0x00000064) components
2017-11-05 21:26:04, Info                  CSI    0000016f [SR] Beginning Verify and Repair transaction
2017-11-05 21:26:26, Info                  CSI    00000171 [SR] Verify complete
2017-11-05 21:26:27, Info                  CSI    00000172 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:26:27, Info                  CSI    00000173 [SR] Beginning Verify and Repair transaction
2017-11-05 21:26:49, Info                  CSI    00000175 [SR] Verify complete
2017-11-05 21:26:58, Info                  CSI    00000176 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:26:58, Info                  CSI    00000177 [SR] Beginning Verify and Repair transaction
2017-11-05 21:27:05, Info                  CSI    00000179 [SR] Verify complete
2017-11-05 21:27:05, Info                  CSI    0000017a [SR] Verifying 100 (0x00000064) components
2017-11-05 21:27:05, Info                  CSI    0000017b [SR] Beginning Verify and Repair transaction
2017-11-05 21:27:22, Info                  CSI    0000017d [SR] Verify complete
2017-11-05 21:27:23, Info                  CSI    0000017e [SR] Verifying 100 (0x00000064) components
2017-11-05 21:27:23, Info                  CSI    0000017f [SR] Beginning Verify and Repair transaction
2017-11-05 21:27:32, Info                  CSI    00000181 [SR] Verify complete
2017-11-05 21:27:32, Info                  CSI    00000182 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:27:32, Info                  CSI    00000183 [SR] Beginning Verify and Repair transaction
2017-11-05 21:27:43, Info                  CSI    00000185 [SR] Verify complete
2017-11-05 21:27:46, Info                  CSI    00000186 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:27:46, Info                  CSI    00000187 [SR] Beginning Verify and Repair transaction
2017-11-05 21:27:58, Info                  CSI    00000189 [SR] Verify complete
2017-11-05 21:28:02, Info                  CSI    0000018a [SR] Verifying 100 (0x00000064) components
2017-11-05 21:28:02, Info                  CSI    0000018b [SR] Beginning Verify and Repair transaction
2017-11-05 21:28:30, Info                  CSI    0000018d [SR] Verify complete
2017-11-05 21:28:30, Info                  CSI    0000018e [SR] Verifying 100 (0x00000064) components
2017-11-05 21:28:30, Info                  CSI    0000018f [SR] Beginning Verify and Repair transaction
2017-11-05 21:28:33, Info                  CSI    00000191 [SR] Verify complete
2017-11-05 21:28:34, Info                  CSI    00000192 [SR] Verifying 100 (0x00000064) components
2017-11-05 21:28:34, Info                  CSI    00000193 [SR] Beginning Verify and Repair transaction
2017-11-05 21:28:46, Info                  CSI    0000019e [SR] Verify complete
2017-11-05 21:28:48, Info                  CSI    0000019f [SR] Verifying 71 (0x00000047) components
2017-11-05 21:28:48, Info                  CSI    000001a0 [SR] Beginning Verify and Repair transaction
2017-11-05 21:28:51, Info                  CSI    000001a2 [SR] Verify complete
2017-11-05 21:28:51, Info                  CSI    000001a3 [SR] Repairing 0 components
2017-11-05 21:28:51, Info                  CSI    000001a4 [SR] Beginning Verify and Repair transaction
2017-11-05 21:28:51, Info                  CSI    000001a6 [SR] Repair complete
 

...It appears that the message returned from the sfc command is saying that there are corrupt files, but the log file does not show that.... Here is the sfc info:

 

2017-11-05 21:12:59, Info                  CSI    00000006 [SR] Verifying 100 (0x00000064) components

.

.
2017-11-05 21:28:48, Info                  CSI    000001a0 [SR] Beginning Verify and Repair transaction
2017-11-05 21:28:51, Info                  CSI    000001a2 [SR] Verify complete
2017-11-05 21:28:51, Info                  CSI    000001a3 [SR] Repairing 0 components
2017-11-05 21:28:51, Info                  CSI    000001a4 [SR] Beginning Verify and Repair transaction
2017-11-05 21:28:51, Info                  CSI    000001a6 [SR] Repair complete

Hi ray5450:

Run sfc /scannow from an elevated command prompt and then post a screenshot of the scan results.

If you are using an elevated command prompt the title bar should say "Administrator" as shown below.  If the scan returns the message "Windows Resource Protection could not perform the requested operation." you might be able to run a SFC repair from Safe Mode, but only if you have both folders named PendingDeletes and PendingRenames in C:\Windows\Winsxs\Temp  (note: I only have the PendingRenames folder on my Vista SP2 machine as shown below).  See the MS support article Use the System File Checker tool to repair missing or corrupted system files as well as the InfoPackets article How to Fix: 'sfc /scannow' Fails, Won't Complete for more information on running SFC from Safe Mode.

 SFC Scannow Administrator 21 May 2017.png   11.6KB   0 downloads

 SFC Safe Mode PendingRenames Folder.png   23.74KB   0 downloads

...right after the information appears in Speccy, the hard drive read/write light goes on and the mouse becomes unresponsive.  The machine is not completely frozen because the light goes off once in awhile for a second, the clock keeps correct, and the screen goes off from the power options and comes back on with a key press.  However, I cannot do anything else.

If Speccy runs correctly and populates the interface after the program is launched, are you able to navigate through the menu using your touchpad or keyboard (Alt+F) to publish the snapshot (File | Publish Snapshot) when the mouse stops working?  Did you try unzipping the portable version of Speccy (available at http://www.piriform.com/speccy/builds) on a USB thumb drive and running Speccy.exe (32-bit Vista SP2) or Speccy64.exe (64-bit Vista SP2) from the thumb drive?

-----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.4.0 * NS Premium v22.11.0.41 * MB Premium v3.3.1 * Speccy Portable 1.31.732
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS

Edited by lmacri, 07 November 2017 - 02:33 PM.

Hi Ray5450:

The next time you post back could you also confirm that the hard drive you are trying to re-image with ImageX is installed on a Vista SP2 computer?  If so, were you able to confirm that your Vista SP2 OS was fully patched to April 2017 (i.e., the end of extended support for Vista SP2) before you created the image from your original drive?  If your April 2017 Patch Tuesday updates installed correctly the Update Version for your IE9 browser at Help | About Internet Explorer should be v9.0.60 / KB4014661 as shown below.

 IE9 Version KB4014661 April 2017.png   17.66KB   0 downloads

Your July 2017 thread Acer recovery error mentioned that you have a Vista OS but the Speccy snapshot you posted in September 2017 in Directdraw incompatible? is for a Win 7 SP1 notebook.

The October 2017 Monthly Rollup Preview for Windows 7 (KB4041686, released 17-Oct-2017) re-introduced a known bug for System File Checker (SFC) - see Woody Leonhard's article Big problems With Win7 Preview of Monthly Rollup KB4041686 on his AskWoody.com site - and if you installed this Monthly Preview on a Win 7 SP1 machine a SFC scan would likely trigger a "bogus SFC error".
-----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.4.0 * NS Premium v22.11.0.41 * MB Premium v3.3.1 * Speccy Portable 1.31.732
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS

Edited by lmacri, 07 November 2017 - 08:22 PM.

Thank-you, for your reponse.

I ran sfc as administrator and received the same results.  I can make a screen shot, but I do not know how to upload it to my post like you did--how did you do that?  Anyway, I can post a copy:

"Microsoft Windows [Version 6.0.6002] Copyright © 2006 Microsoft Corporation.  All rights reserved.

C:\>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of them.

Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log

C:\Users\Rodd>sfc /scannow"

(Again, the log does not show any corrupt files or "cannot repair"'s)

I ran portable Speccy from flashdrive with the same results.  It took a long time, but I was able to make and copy the link, then close Speccy.  As soon as it closed, all was normal again.  Since it has never done this before, I can only conclude that something with my system is causing it do do that...but what?

http://speccy.piriform.com/results/j0DbFKZu2bMJzQLKbkUoyMV

No, I am not affected by any Windows 7 updates.  This is a Vista sp2 machine.  My previous post you found regarding Acer was this same Vista machine when I first started building the drive to make the image.  My post regarding directdraw was my Windows 7 machine, which I am not using anymore because the cord is broken and the fan is wearing out---maybe I'll fix it someday.

I ran portable Speccy from flashdrive with the same results.  It took a long time, but I was able to make and copy the link, then close Speccy.  As soon as it closed, all was normal again.  Since it has never done this before, I can only conclude that something with my system is causing it do do that...but what?

http://speccy.piriform.com/results/j0DbFKZu2bMJzQLKbkUoyMV

 

No, I am not affected by any Windows 7 updates.  This is a Vista sp2 machine.  My previous post you found regarding Acer was this same Vista machine when I first started building the drive to make the image....

Hi ray5450:

Was the ImageX image you applied to this machine captured after a clean re-install of Vista SP2?  You didn't answer my question in post # 7 about whether your IE9 browser is patched to v9.0.60 / KB4014661, but your Speccy profile shows you still have Internet Explorer 7 (released October 18, 2006), which is the old version of IE that came bundled with SP2 when SP2 was released back in May 2009.  I also can't see any evidence that available security updates have been applied since SP2 was installed so if my suspicions are correct you could have ~ 180 to 200 Windows security updates pending on this computer.  The System Processes section at the bottom of your Speccy profile shows multiple processes trying to making connections through your firewall, and a few could be associated with background automatic updates attempting to apply available updates to your software programs.

It also looks like there are also quite a few outdated hardware drivers that need to be updated.  For example, the Synaptics PS/2 Port Pointing Device driver for your wonky mouse is v10.0.15.0 (released 07-Sep-2007) while my Vista SP2 machine currently has v15.3.29.0 (released 13-Oct-2011).

Please step through instructions on page 1 of m#l's thread Updates not working, it has been searching for updates for hours to see if you are affected by this slow Windows Update problem. There are five security updates listed in STEP # 2 of those instructions [KB3205638 (rel. 13-Dec-2016); KB4012583 (rel. 14-Mar-2017); KB4015195, KB4015380 and KB4014661 (rel. 11-Apr-2017)] and if any of those five updates are currently missing from your system they will have to be manually installed before Windows Update will run to completion and patch your Vista SP2 OS as of April 2017.

Note that KB4014661 is the April 2017 cumulative security update for IE9, so to save yourself some time later in the process you might want to upgrade from IE7 to IE9 first and then apply KB4014661 along with the other Windows Update speed up patches when you reach STEP # 3 of the instructions in m#l's thread .  Go to https://www.microsoft.com/en-ca/download/internet-explorer-9-details.aspx - that download page should automatically detect that you have 32-bit Vista and offer the correct IE9 installer released back in 2011.

Also note that the problems with Windows Update are more prevalent on computers with slow CPUs and low amounts of RAM.   Your Acer computer has a Celeron M 530 CPU @ 1.73GHz (which I believe is a single core CPU) and only 2 GB of RAM, and if the Vista SP2 Windows Update Agent v7.6.7600.256 (C:\Windows\System32\wuaueng.dll, last updated June 2012) hangs on "Checking for updates..." it will saturate an entire core of your CPU (but will not thrash your hard drive with reads/writes) for several hours, or even days, and cause all sorts of performance issues on your computer.

-----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.4.0 * NS Premium v22.11.0.41 * MB Premium v3.3.1 * Speccy Portable 1.31.732
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS

Edited by lmacri, 08 November 2017 - 09:41 AM.

Yes, all that is installed is Vista sp2 and all the updates at the time I first started making an image.

The problem is not Windows update trying to run or install updates because I turned off automatic updates when I did the install.

I'm not sure why drivers and updates would affect imagex.  Imagex has been around since before any updates.  When my original drive works fine, I'm looking to have the image work the same....but it is not.  That is the issue.

Thanks.

Yes, all that is installed is Vista sp2 and all the updates at the time I first started making an image.  The problem is not Windows update trying to run or install updates because I turned off automatic updates when I did the install. 

 

I'm not sure why drivers and updates would affect imagex.

Hi Ray5450:

It's the same image but different hardware.  I was just wondering if patching your Vista SP2 OS system files and hardware drivers (including the drivers for your Toshiba MQ01ABD050 hard drive) might change the behaviour of SFC with your newer hard drive.

You'll have wait for someone with experience with ImageX and/or stress testing of hard drives to jump in and see what they can suggest.  Alternately, you could try cloning your old hard drive with Macrium Reflect Free and see if SFC runs correctly when you re-image the new drive with a Macrium Reflect image.  I've posted links to tutorials <here> on how to swap out entire hard drives using Macrium Reflect Free but the Speccy profile <here> for your Win 7 SP1 computers shows you had Macrium Reflect services running on that computer, so you're probably already familiar with that disk imaging and cloning software.

Good luck, and hope you find a solution soon.  Sorry if I've wasted your time.

-----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.4.0 * NS Premium v22.11.0.41 * MB Premium v3.3.1 * Speccy Portable 1.31.732 * Macrium Reflect Free 7.1.2654
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS

Edited by lmacri, 08 November 2017 - 01:57 PM.

...I can make a screen shot, but I do not know how to upload it to my post like you did--how did you do that?

Hi ray5450:

I just realized I never answered your question about inserting images in a reply.

Click the More Reply Options button at the bottom of the WYSIWYG editor (next to the Post button) and then scroll down to the Attach Files section. Browse to the location of the image on your hard drive, click Open to upload, and then click the Attach This File button.  After it's attached, click your cursor where you want to add the image and select the Add to Post link next to the thumbnail.

 bleepingcomputer Add Image to Posts.png   15.28KB   0 downloads

When you're editing a post the button label changes from More Reply Options to Use Full Editor.

-----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.4.0 * NS Premium v22.11.0.41 * MB Premium v3.3.1 * Speccy Portable v1.31.732 * Macrium Reflect Free v7.1.2654
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS

Edited by lmacri, 08 November 2017 - 03:02 PM.

No, you did not waste my time.  I am greatful for all information to try.  I also appreciate the effort you took to go through my old posts.

I built the drive on a Hitachi.  Next, I made a practice image transfer to a Toshiba and it worked fine (no sfc errors, etc.).  Now, I am trying to transfer it to a bigger Toshiba, which is this problem.

I have used Macrium, yes.  I am trying to use imagex because the image size is a lot smaller than with Macrium, it does not take as long to appy images, and I only need one boot cd.

Thanks, for the attachment information.

Yes, I hope also that I get more information for this issue.

Something else just happened.  In order to investigate this sfc issue, I decided to just start over and try again and made a new image, but I did not change the original drive.  When  I apply the image, most of the shortcuts are missing from the start menu, and I do not know what else may potentially be missing.  I have tried many times to re-image and re-apply, varying anything I can find, but it always turns out this way.  I do not know how it worked the first time.  The original drive works fine.

Has anyone heard of this, and/or know how to fix it?  Thanks.

Imacri:  you asked me if the problems were from the imagex-made image.  When I said "yes and no", I should have said, maybe yes, maybe no, because I wanted to test the original drive for these same problems.  I had already done sfc, so I did not (at first) repeat it on the newest install that I mentioned in my above previous post (I said the original drive works fine, because the previous one did).  I then decided to do it anyway, and now it is getting corrupted files in the log.  This is not an image copy but an install directly from the mfr recovery disks with no changes.    I repeated (3rd) the install with the same results.

"Found: {l:32 b:KIxPEr33r1OAJK4106/Q3+Fa2NvSHVJMBjykzdV475h=} Expected: {l:32 b:40ijQez8dnId2/xBxTWnf/gsCddJvRLR5cH9MDStaEu=}
2017-11-22 06:05:02, Info                  CSI    000000ed [SR] Cannot repair member file [l:24{12}]"settings.ini" of Microsoft-Windows-Sidebar, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2017-11-22 06:05:07, Info                  CSI    000000ee Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6000.16386_none_cca5e9c129bd0a02\settings.ini do not match actual file [l:24{12}]"settings.ini"

There are 3 more corrupt entries regarding Sidebar. 

My goal is to create a perfect image, eventually with updates, preferably with imagex--if it is possible, but first, before using any imager, I need the original to not have any problems.  In the meantime, since this is the only machine I have right now, I've just been trying to get a working disk to function the best it can.

What do you think about these corruptions?  I don't use Sidebar and I shut it off, but why is this happening?  Could it affect anything else?

Thanks.