Windows 10: Hashes for file member [l:11]'msadomd.dll' do not match

I'm unable to open photos with the default Windows Photo App, keeps giving me a "the package runtime information is corrupted" error notification. So I did an sfc/scannow scan and it came up with 1 file that couldn't be repaired, the msadomd.dll file.
Not sure if they're a related issue.

Going to also leave with this:

Could not reproject corrupted file \??\C:\Program Files (x86)\Common Files\System\ado\\msadomd.dll; source file in store is also corrupted

:)

 

SFC error UNIDRVUI.DLL Version = 10.0.10240.16384 Hash Mismatch after Windows 10 updates 11/10 thru 11/11/2015

Following errors appeared in sfcdetails.txt on 11/11/2015 (after Windows 10 updates 11/10 thru 11/11/2015)

This error occurred on ALL of my Windows 10 based PC's on the same day "Today"

2015-11-11 11:02:49, Info CSI 00005600 [SR] Beginning Verify and Repair transaction

2015-11-11 11:02:49, Info CSI 00005602 [SR] Cannot repair member file [l:36{18}]"Amd64\UNIDRVUI.DLL" of ntprint.inf, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate"
in the store, hash mismatch

2015-11-11 11:02:49, Info CSI 00005605 [SR] Cannot repair member file [l:36{18}]"Amd64\UNIDRVUI.DLL" of ntprint.inf, Version = 10.0.10240.16384, pA = amd64, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type = [l:24{12}]"driverUpdate"
in the store, hash mismatch

2015-11-11 11:02:49, Info CSI 00005606 [SR] This component was referenced by [l:248{124}]"Microsoft-Windows-Client-Drivers-printscan-Package~31bf3856ad364e35~amd64~~10.0.10240.16384.280a92fe8216a0b6f7a3fefdb8439557"

Any advice or suggestions greatly appreciated!

UPDATE: a Fix would be is the best answer.

Otherwise should I worry about it?

Will this be fixed by MS via the Update process?

Dennis

 

mfc90.dll mismatch in win10 pro -SFC finds error on Microsoft.VC90.MFC:how to repair

Hi,

I am searching a bad problem with effects:

Windows blue screen with error: FAULTY_HARDWARE_CORRUPTED_PAGE
I have tried possible solution(How to fix Faulty Hardware Corrupted Page Error in Windows?) found on Google. But the "Method 1: Disabling fast startup" in the above hyperlink didn't work, nor did the "Running a RAM Check in Method 2. When I tried "Running
System File Checker" in Method 2 with "sfc /scannow" command, the system found errors on Microsoft.VC90.MFC:

2018-12-11 18:10:12, Info CSI 00005c42 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_044aad0bab1eb146\mfc90.dll do not match actual file [l:18{9}]"mfc90.dll" :

Found: {l:20 b:yqBKnH+3MerlDTAxpfv/VS4ubb8=} Expected: {l:20 b:5NGq7xbYnlMyzxK8ozoR2ij7isI=}

Found: {l:20 b:XWTO/HvyZ1PeSy491D/9/Gbejdo=} Expected: {l:20 b:AnYAaoEDS8oZtuFV9gllFhXss5I=}

2018-12-11 18:10:12, Info CSI 00005c43 [SR] Cannot repair member file [l:18{9}]"mfc90.dll" of Microsoft.VC90.MFC, Version = 9.0.30729.6161, pA = amd64, , PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32" in the store,
hash mismatch

2018-12-11 18:10:12, Info CSI 00005c44@2018/12/11:10:10:12.938 Primitive installers committed for repair

2018-12-11 18:10:13, Info CSI 00005c45 Hashes for file member \SystemRoot\WinSxS\amd64_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.6161_none_044aad0bab1eb146\mfc90.dll do not match actual file [l:18{9}]"mfc90.dll" :

Found: {l:20 b:yqBKnH+3MerlDTAxpfv/VS4ubb8=} Expected: {l:20 b:5NGq7xbYnlMyzxK8ozoR2ij7isI=}

Found: {l:20 b:XWTO/HvyZ1PeSy491D/9/Gbejdo=} Expected: {l:20 b:AnYAaoEDS8oZtuFV9gllFhXss5I=}

2018-12-11 18:10:13, Info CSI 00005c46 [SR] Cannot repair member file [l:18{9}]"mfc90.dll" of Microsoft.VC90.MFC, Version = 9.0.30729.6161, pA = amd64, , PublicKeyToken = {l:8 b:1fc8b3b9a1e18e3b}, Type = [l:10{5}]"win32" in the store,
hash mismatch

2018-12-11 18:10:13, Info CSI 00005c47 [SR] This component was referenced by [ml:38{19},l:36{18}]"Windows Foundation"

2018-12-11 18:10:13, Info CSI 00005c48@2018/12/11:10:10:13.019 Primitive installers committed for repair

2018-12-11 18:10:13, Info CSI 00005c49 [SR] Repair complete

HELP, how to repair?

Can this error be the cause of the system blue screen errors found?

Best regards

 

msls31.dll Error

Just upgraded from Windows 8.1 to Windows 10 via USB media creation tool. After installing programs from Steam, two of them have sub applications that use msls31.dll but programs games have the following error display when starting them:



I have followed the advice (with exception to reinstalling Windows) from the following two sources but still have no success of identifying the problem.

Fix Msls31.dll Error - Instant-Registry-Fixes.org

https://support.microsoft.com/en-us/kb/929833

After running the "sfc /scannow" command in command prompt, the follow log was created pertaining to msls31.dll:

-----------------------------------------------------------------------------------------------------------------------------

Info CSI 00005015 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-msls31_31bf3856ad364e35_11.0.10240.16384_none_220d03aa9af66273\msls31.dll do not match actual file [l:20{10}]"msls31.dll" :

Found: {l:32 b:/7qmfYZclIU4NhTTEq73qnhMNosCZzZs/CL0OjApFAM=} Expected: {l:32 b:0kwj6yIT4uROorHi9rLJHaNFTda91LvSKa0HivlCXN8=}

2015-08-05 22:36:10, Info CSI 00005016 [SR] Cannot repair member file [l:20{10}]"msls31.dll" of Microsoft-Windows-MSLS31, Version = 11.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store,
hash mismatch

2015-08-05 22:36:10, Info CSI 00005017@2015/8/6:03:36:10.714 Primitive installers committed for repair

2015-08-05 22:36:10, Info CSI 00005018 Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-msls31_31bf3856ad364e35_11.0.10240.16384_none_220d03aa9af66273\msls31.dll do not match actual file [l:20{10}]"msls31.dll" :

Found: {l:32 b:/7qmfYZclIU4NhTTEq73qnhMNosCZzZs/CL0OjApFAM=} Expected: {l:32 b:0kwj6yIT4uROorHi9rLJHaNFTda91LvSKa0HivlCXN8=}

2015-08-05 22:36:10, Info CSI 00005019 [SR] Cannot repair member file [l:20{10}]"msls31.dll" of Microsoft-Windows-MSLS31, Version = 11.0.10240.16384, pA Host= amd64 Guest= x86, nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35} in the store,
hash mismatch

2015-08-05 22:36:10, Info CSI 0000501a [SR] This component was referenced by [l:370{185}]"Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-windows~31bf3856ad364e35~amd64~~10.0.10240.16384.Microsoft-Windows-Client-Features-WOW64-Package-AutoMerged-windows-Deployment"

2015-08-05 22:36:10, Info CSI 0000501b Hashes for file member \??\C:\WINDOWS\SysWOW64\msls31.dll do not match actual file [l:20{10}]"msls31.dll" :

Found: {l:32 b:/7qmfYZclIU4NhTTEq73qnhMNosCZzZs/CL0OjApFAM=} Expected: {l:32 b:0kwj6yIT4uROorHi9rLJHaNFTda91LvSKa0HivlCXN8=}

2015-08-05 22:36:10, Info CSI 0000501c Hashes for file member \SystemRoot\WinSxS\wow64_microsoft-windows-msls31_31bf3856ad364e35_11.0.10240.16384_none_220d03aa9af66273\msls31.dll do not match actual file [l:20{10}]"msls31.dll" :

Found: {l:32 b:/7qmfYZclIU4NhTTEq73qnhMNosCZzZs/CL0OjApFAM=} Expected: {l:32 b:0kwj6yIT4uROorHi9rLJHaNFTda91LvSKa0HivlCXN8=}

2015-08-05 22:36:10, Info CSI 0000501d [SR] Could not reproject corrupted file [ml:48{24},l:46{23}]"\??\C:\WINDOWS\SysWOW64"\[l:20{10}]"msls31.dll"; source file in store is also corrupted

2015-08-05 22:36:10, Info CSI 0000501e@2015/8/6:03:36:10.740 Primitive installers committed for repair

2015-08-05 22:36:10, Info CSI 0000501f [SR] Repair complete

-----------------------------------------------------------------------------------------------------------------------------

I am unsure what exactly this means but the problem still persist when trying to run the programs.

Please advise on an appropriate course of action that I should take.

Thank you.