2020 VALIDATION ERROR (corrupt)
OK so here we go yet again!
This started when I had the 2019 version same issue, done months of test and submitted to the Acronis engineering team.
I was told there investigating it and would let me know when they had a fix.
Just a fyi I had run every intense text that they wanted me to to. memory, HD and everything else they asked, sent log files and hours and hours of time online and live. They did determine that there was nothing wrong with my pc.
So after just about a year of this I contacted them if they had ever fixed the issue, this whole time I was told they would contact myself.
Well the fix was the 2020 version, that worked for awhile.
My pc is a Dell Studio D540 running Win 7 64 Home w/ 8 gb ram. Well that PC died last week, I suspect that it was the power supply.
While on Ebay I saw the same model with the exception of that came from the factory with Win 7 64 Pro installed ( with OEM Dell install and driver discs) and only had 6gb ram. My 540 that died started out as a Vista that was upgraded to the Win7 home.
So bough the pc off Ebay, put my 1tb HD in it and upgraded the OS using the WIn COA 7 sticker SN to go to pro. next was to upgrade my ram to 8gb and poop in my 2tb slave drive.
Went into the Dell site and ran there diagnostic program to make sure all was well and passed both times w. flying colors.
Now off to the Acronis site to move my 2020 version to this pc. Now feeling great all was going so smooth.
Ran the Acronis as a single version w/ validation and that went smooth and it validated.
Next day not so good would not validate (backup is corrupt) so here we go again, got online with Acronis and did a remote and the tech ran all kinds of tests and get the same answer. (BTW The tech was able to run it once and validate it and that was it!)
Going to submit to the engineering dept and will get back Mon or Tues. In the meantime he said just to keep on running backups and it may clear itself ( that I may have misunderstood) as well as try backing up to a different drive, I did try a 128gb Transcend thumb drive and that was the same issue.
On my own I have run the chkdsk as well as sfc scannow and no issues what so ever plus the complete set of Dell diagnostics.
At this point DeJa Vu.
Has anyone experienced anything like that and have they come up with a fix?
In the meantime will wait to see what the engineers come up with.
Please do not ask me to post test results here, this is more of a nice vent and to see if anyone had this issue and how it or if it was ever resolved.?
Need some answers if possible???
TIA
Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For example
C:\Windows\Logs\CBS\CBS.log
The log is written to the above folder automatically by the SFC ScanNow tool.
Interpretting the CBS.log is a different story...! I can only suggest searching within the log file for words such as 'corrupt' or 'error' etc and see what it shows you?
Sometimes, it can take several attempts of SFC /Scannow before it is able to complete - it's taken me up to 5 times in some instances.
Alternatively, if it simply fails to repair them with the error:
Windows Resource Protection found corrupt files but was unable to fix some of them.
Then the next step is to run a dism online cleanup, reboot and then run sfc again.
This is the tutorial I follow in this case and it has worked fine a couple of times now.
https://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image
I,am unable to run the DISM?? ( Does Acronis offer support to fix this free or paid?) Iam at a dead end here????
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>DISM /Online /Cleanup-Image /CheckHealth
Deployment Image Servicing and Management tool
Version: 6.1.7601.24499
Image Version: 6.1.7601.24499
Error: 87
The checkhealth option is not recognized in this context.
For more information, refer to the help.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
C:\Windows\system32>DISM /Online /Cleanup-Image /ScanHealth
Deployment Image Servicing and Management tool
Version: 6.1.7601.24499
Image Version: 6.1.7601.24499
Whole Dism too large to put here, last few lines
commands from provider: DISM Unattend Manager
2019-10-17 06:26:49, Info DISM DISM.EXE: Succesfully registered commands for the provider: DISM Unattend Manager.
2019-10-17 06:26:49, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
2019-10-17 06:26:49, Info DISM DISM.EXE: Attempting to add the commands from provider: SmiManager
2019-10-17 06:26:49, Info DISM DISM.EXE: Attempting to add the commands from provider: Edition Manager
2019-10-17 06:26:49, Info DISM DISM Transmog Provider: PID=8284 Current image session is [ONLINE] - CTransmogManager::GetMode
2019-10-17 06:26:49, Info DISM DISM.EXE: Succesfully registered commands for the provider: Edition Manager.
2019-10-17 06:26:49, Info DISM DISM Provider Store: PID=8284 Getting Provider DISM Package Manager - CDISMProviderStore::GetProvider
2019-10-17 06:26:49, Info DISM DISM Provider Store: PID=8284 Provider has previously been initialized. Returning the existing instance. - CDISMProviderStore::Internal_GetProvider
2019-10-17 06:26:49, Info DISM DISM Package Manager: PID=8284 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::Private_ValidateCmdLine
2019-10-17 06:26:49, Info DISM DISM Package Manager: PID=8284 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2019-10-17 06:26:49, Info DISM DISM Package Manager: PID=8284 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2019-10-17 06:26:49, Info DISM DISM Package Manager: PID=8284 Start running scanhealth. - CDISMPackageManager::ScanHealth
report:
|
Windows Update |
Publisher details |
| Issues found | ||
|
Service registration is missing or corrupt Service registration is missing or corrupt |
Fixed |
 |
|
||
|
Windows Update error 0x80070057(2019-10-17-T-06_18_25A) Windows Update error 0x80070057(2019-10-17-T-06_18_25A) |
Fixed |
|
|
||
|
Problems installing recent updates Problems installing recent updates |
Fixed |
|
|
||
|
Problems installing recent updates Problems installing recent updates |
Fixed |
|
|
| Potential issues that were checked | ||
|
Windows Update environment variables are incorrect Windows Update environment variables are incorrect |
Issue not present |
|
|
Some security settings are missing or have been changed Some security settings are missing or have been changed |
Issue not present |
|
|
Check for missing or corrupt files Check for missing or corrupt files |
Issue not present |
|
|
Windows Update services are not running Windows Update services are not running |
Issue not present |
|
|
Cryptographic service components are not registered Cryptographic service components are not registered |
Issue not present |
|
Issues found |
Detection details |
|
||||
|
|
|||||||||
|
|
||||
|
|
||||
|
|
Potential issues that were checked |
Detection details |
|
||||
|
||||
|
||||
|
||||
|
||||
|
Detection details |
|
|
Error Report |
||||||
|
|
Collected File |
||
|
| Collection information | |
| Computer Name: | STUDIO |
|---|---|
| Windows Version: |
6.1 |
| Architecture: |
amd64 |
| Time: |
Thursday, October 17, 2019 6:17:46 AM |
|
Publisher details |
|
| Background Intelligent Transfer Service | |
| Find and fix problems that may prevent background downloads from working | |
| Package Version: |
1.2.1.20140627 |
|---|---|
| Publisher: |
Microsoft Corporation |
| Windows Update | |
| Find and fix problems with Windows Update | |
| Package Version: |
8.1.1.20160515 |
|---|---|
| Publisher: |
Microsoft Corporation |
| Windows Update | |
| Find and fix problems with Windows Update | |
| Package Version: |
8.1.1.20160515 |
|---|---|
| Publisher: |
Microsoft Corporation |
BTW the above report all shown are checked off as fixed? Please see the attached PDF in the previous post.
At this point if this can be fixed I would pay for it , at my wits end. Also I have completely uninstalled Acronis 2020 and wad going to reinstall but again do not know how, but a this point I really dout it would fix anything
Ran the DIS,M and got this?:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>DISM /Online /Cleanup-Image /ScanHealth
Deployment Image Servicing and Management tool
Version: 6.1.7601.24499
Image Version: 6.1.7601.24499
................................................................................
................................................................................
................................................................................
................................................................................
................................................................................
..........................................Completed running scanhealth, check lo
gs at %windir%\logs\CBS\Checksur.log
The operation completed successfully.
C:\Windows\system32>DISM /Online /Cleanup-Image /CheckHealthDISM /Online /Cleanu
p-Image /RestoreHealth
Error: 87
The Online option has been duplicated on the command-line.
Remove the duplicate option and try the command again.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
C:\Windows\system32>DISM /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 6.1.7601.24499
Image Version: 6.1.7601.24499
Error: 87
The restorehealth option is not recognized in this context.
For more information, refer to the help.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
C:\Windows\system32>
Dism report end and full report is attached:
2019-10-17 07:49:19, Info DISM DISM Image Session: PID=1100 Disconnecting the provider store - CDISMImageSession::Final_OnDisconnect
2019-10-17 07:49:19, Info DISM DISM Provider Store: PID=1100 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
2019-10-17 07:49:19, Info DISM DISM Provider Store: PID=1100 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
2019-10-17 07:49:19, Info DISM DISM Provider Store: PID=1100 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
Given you had issues with Windows Update I would recommend that you run Windows Update Troubleshooter tool on your machine to address issues that may be present that DISM could not or did not detect/fix.
You can download the troubleshooter tool HERE
On the link page tick the circle for Windows 7 to get the right version of the tool. Follow the instruction there to download the tool and run it.
I have had issues with Windows Update that nothing could fix except this tool. Your situation mimics my experiences.
You entered the wrong command as:
DISM /Online /Cleanup-Image /CheckHealthDISM /Online /Cleanup-Image /RestoreHealth.
Typically, you do each one in order, working your way up...
DISM /Online /Cleanup-Image /CheckHealthDISM
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth
You need to remove the checkhealth portion and only use just the switch with /RestoreHealth as the command used above is incorrect. Just enter:
DISM /Online /Cleanup-Image /RestoreHealth
Ran the restore health and go this:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>DISM /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 6.1.7601.24499
Image Version: 6.1.7601.24499
Error: 87
The restorehealth option is not recognized in this context.
For more information, refer to the help.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
C:\Windows\system32>
if you're unable to run it from the OS, my best guess is you have either some type of OS corruption and/or your Windows Recovery environment is also messed up or missing.
See if your Windows rescue environment is enabled or found. under admin command prompt:
reagentc /info
should look something like this if it is found and working
C:\windows\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:
Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk1\partition4\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: a5015b3f-edcb-11e9-95c0-408d5c563e3d
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0
REAGENTC.EXE: Operation Successful.
I guess we're getting away from the actual validation issue, but these steps may be identifying an underlying issue in the OS (despite being a fairly new upgrade) that are a little deeper.
From what I have seen online quite a few folks have this issue???
Also I did have my Dell OS re-innstallation disc I ran that is repair mode and it looks like the only repair that you can run is the start up, I did run it through and then used the dos prompt and ran the SFC/scannow and it came up that there is 1 thing found and waiting for repair .
They it said to restart the PC and then the scannow again. Did this a few times and still no luck.
The next strange thing was that I had a extra blank HD so I tried reinstall the OS on that, after it was installed but I had nothing else installed on the pc I tried the scannow and I got the same corrupt message???
Now that is very strange???
The disc came with the PC and was still sealed from the factory..
Little more info my original PC was the Studio 540 running Win7 64 Home and that died. I came across on LN one on Ebay w/o the HD but did come with the Dell Win7 software. I asked on 7 Forums since the PC's were the same if I could just swap HD from my old one, I was told if the new PC did have the the MS Win7 COA sticker on it (which it did) allI would have to do after the swap to put in the Win7 64 Home premium number it it would update my HD to that. So I did that and it registered the update w/o any issue...
So here is where Im at, again could this be some type of strange malware???
Never saw this before and its a strange on expecially when I got the same error with a different HD and a fresh Win7 install???
Sorry it looks not to be:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>C:\windows\system32>reagentc /info
'C:\windows\system32' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\system32>Windows Recovery Environment (Windows RE) and system reset c
onfiguration
'Windows' is not recognized as an internal or external command,
operable program or batch file.
C:\Windows\system32>Information:
Escorial,
Is this re-installation media you have a Dell product? Something that they may have sent you or that you got with the purchase of your Dell PC?
Have you considered installing a genuine Windows 7 and see how that works? There is a download tool available that when run accesses Microsofts TechBench site where a number of MS product download ISO files can be found. You can burn these ISO files to a CD and install them then use you product key for activation. If activation fails you can use the Microsoft phone activation to get things working.
Here is a link to the download tool Windows Downloader tool
Another thought here is that DISM was not a part of Windows 7. It was offered up as a Windows Update KB947821
Have you checked to see if that update is installed on your machine? If not then I would suggest that you download and install it then try the DISM commands again. If it is installed I would recommend that you uninstall it, reboot the PC and then re-install the update again then once installed try the DISM commands again.
Get the KB947821 HERE
Enchantech - ooooof, I didn't even catch that this was Windows 7 off the build number (doh). You're right, DISM repair does not work on Windows 7. I'm not really sure how to fix Windows 7 failure to run sfc /scannow either then.
The best way that I found of repairing issues in Windows 7 was to do an in-place upgrade using the same Win 7 SP1 media then go through all the pain of reapplying all missing Windows Updates that had come after that SP pack.
The key with the in-place upgrade is to run the setup.exe from the media from within Windows so that it is an upgrade. If done from booting the media, then everything gets wiped out for a clean start.
Yes that does look good on mine. Is there any way Acronis could of caused this?
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>reagentc /info
Extended configuration for the Recovery Environment
Windows RE enabled: 1
Windows RE staged: 0
Setup enabled: 0
Custom Recovery Tool: 0
WinRE.WIM directory:
Recovery Environment: \\?\GLOBALROOT\device\harddisk0\partition2\Recovery\46
1ef153-4a94-11e4-b214-b8d3dd840d71
BCD Id: 461ef153-4a94-11e4-b214-b8d3dd840d71
Setup Files:
Recovery Operation: 4
Operation Parameter:
Boot Key Scan Code 0x0
REAGENTC.EXE: Operation successful
C:\Windows\system32>
Bobbo_3C0X1 wrote:if you're unable to run it from the OS, my best guess is you have either some type of OS corruption and/or your Windows Recovery environment is also messed up or missing.
See if your Windows rescue environment is enabled or found. under admin command prompt:
reagentc /info
should look something like this if it is found and working
C:\windows\system32>reagentc /info
Windows Recovery Environment (Windows RE) and system reset configuration
Information:Windows RE status: Enabled
Windows RE location: \\?\GLOBALROOT\device\harddisk1\partition4\Recovery\WindowsRE
Boot Configuration Data (BCD) identifier: a5015b3f-edcb-11e9-95c0-408d5c563e3d
Recovery image location:
Recovery image index: 0
Custom image location:
Custom image index: 0REAGENTC.EXE: Operation Successful.
I guess we're getting away from the actual validation issue, but these steps may be identifying an underlying issue in the OS (despite being a fairly new upgrade) that are a little deeper.
The Windows error 87 is most often related to Windows Update failures. That is why I linked to the KB above. It is officially known as "The System Update readiness tool" It will repair broken Windows update routine.
Here is a link to the MS Knowledge Base article for repairing a Windows 7 installation which should fix the System error 87 issue. KB Article
Follow the instructions
I have already been running that tool and started receiving updates as of yesterday.
Alright, have you ran SFC /scannow from an Admin command prompt to check for corrupted system files since you have gotten updates working?
If SFC reports no corruption then your Win 7 installation is fine. At that point you should run True Image again only this time create a new backup task and DO NOT select Validate Backup in the Options Advanced tab. Run the backup and see if it completes.
Once the backup completes, you can then run Validation from a right click context menu by clicking on the backup task name.
If all is well the validation should pass.
At this point it's still failing the scan now with the same message.
Have run the update fixing and now back to the update not fixed.
For software all I have is the Dell reinstallation win7 disc.
As mentioned before I tried a fresh install on a empty hd I had, after just installing the windows 7 I ran the scan now and got the same validation corrupt message, which again is strange.
At this point as much as I do not want to would anyone think if I just bought a win10 disc.and installed that would that possibly fix this mess?
I do not think this is a hardware issue? Could it be?
I have run thr memory, and HD tests and they all passed.
Also I had win7 sp1 disc.and tried to reload.the servicepack 1 and it would not let me do that either(that was on the original HD)
At a total loss, virus, malware or video curse..
Given that Windows 7 will be unsupported and potentially at greater risk from January 2020, I would definitely recommend making a clean start with Windows 10.
If you are able to boot to the Windows 7 desktop, then you do not need to buy Windows 10 as you can still get a free upgrade from Windows 7 to 10.
To do this: go to the Windows 10 Download webpage - then click on the Update Now button to download the Windows Update Assistant, then run the assistant to perform the upgrade. This will also confirm that your computer meets the requirements for the upgrade.
Once you have upgraded to Windows 10 and activated the software, you can then reinstall it or do a clean install of it if you want to.
Can that download be put on a disc and run from that? I would like to install that on my other empty HD.
Can I use the Win7 MS COA key off my PC or do I have to buy key? I see them for sale on Ebay.
Also updates working but still a fail on the scannow.....
On the same Microsoft webpage above, you can use the Microsoft Media Creation tool to create USB install media but in order to get the free upgrade from Win 7 to 10, you must run the setup application from the Win 7 Desktop.
You do not need the Win 7 COA key provided it has been Activated successfully, and do not need to buy a Win 10 key, as it should be Activated automatically as a free upgrade.
Thank you, hope this fixes the issue...
This is the weirdest thing I have seen in years,,,,,,,,,,,,,
Just a follow up, tried to update to Win10 was not allowed due to something with my graphics card. see below:
"ATI Radeon HD 4300/4500 Series
(ATI Technologies Inc.)
You'll have problems with your display in Windows 10."
So will just leave this pc the way it is. My resolution is 1028x1080 hmm another strange one
Went out and bought a new Dell Alienware R8 running Win10 and that was promptly returned , Win 10 unacceptable and glad my old pc would not let me downgrade to it as that OS is horrible.
So will look for a new/used pc running Win7 ( don't care if its being phased out) rather run that w/o support then run one with win 10.
Thanks all for the effort and patience with myself!
Case closed for now