[SOLVED] Update Win7x64sp1 KB4054518 failed [HRESULT = 0x80070005 - E_ACCESSDENIED]

R

rennyo

Member
Joined
Mar 31, 2018
Posts
9
Hello! Failed to update Win7 Pro on 2 PCs with KB4054518. Last time updated in 01.18. Could you help, please?

CBS.log
****************************************************
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_501_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-1955_neutral_LDR
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_501_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-1955_neutral_LDR, PinDeployment: amd64_30e4bb0a3516678691bb999c2e417dd4_31bf3856ad364e35_6.1.7601.23930_none_a7a9790decb61edf
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_605_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-2553_neutral_LDR
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_605_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-2553_neutral_LDR, PinDeployment: amd64_7d7aece6db87cdaacd1d5a70cdcba23e_31bf3856ad364e35_6.1.7601.23930_none_76ec607c5d659753
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_677_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-2646_neutral_LDR
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_677_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-2646_neutral_LDR, PinDeployment: amd64_e549a5dc8ac729ac34d3875981e2a2e2_31bf3856ad364e35_7.3.7601.23846_none_89d95e65d1770085
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_766_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-2739_neutral_LDR
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_766_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-2739_neutral_LDR, PinDeployment: amd64_7dcaed2a54a5c47b2e7a62f5abfa3f56_31bf3856ad364e35_6.1.7601.23949_none_5ca5d59ba449b2dd
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_795_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-2945_neutral_LDR
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_795_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-2945_neutral_LDR, PinDeployment: amd64_00fa60e96824822ea7ad3bf54873e5f4_31bf3856ad364e35_6.1.7601.23949_none_be5db219337ee962
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_850_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-3079_neutral_LDR
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_850_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-3079_neutral_LDR, PinDeployment: amd64_9970700f564d6cd394a3522e5488d0b7_31bf3856ad364e35_7.3.7601.23885_none_7f0a40f725db8a6b
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_851_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-3080_neutral_LDR
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_851_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-3080_neutral_LDR, PinDeployment: amd64_usbport.inf_31bf3856ad364e35_6.1.7601.23933_none_1c5b39ad335c14a3
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_856_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-3085_neutral_LDR
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_856_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-3085_neutral_LDR, PinDeployment: amd64_c74d3403e79ee11d70d19e20e8854174_31bf3856ad364e35_6.1.7601.23949_none_403d3b3336e6ed22
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_866_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-3095_neutral_LDR
2018-04-01 01:23:17, Info CBS Exec: Staging Package: Package_866_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2, Update: 4054518-3095_neutral_LDR, PinDeployment: amd64_990019bba91c96120f774beb21c7da48_31bf3856ad364e35_6.1.7601.23949_none_6b0f1e1fd201d97a
2018-04-01 01:23:17, Info CSI 00000248@2018/3/31:22:23:17.599 CSI Transaction @0x9415770 destroyed
2018-04-01 01:23:17, Info CSI 00000249@2018/3/31:22:23:17.600 CSI Transaction @0x9415770 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [86]"TI3.30656830_3598567061:3/Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.23964.1.2"

2018-04-01 01:23:18, Error CSI 0000024a@2018/3/31:22:23:18.144 (F) d:\w7rtm\base\wcp\sil\merged\ntu\ntsystem.cpp(703): Error STATUS_ACCESS_DENIED originated in function WorkAroundBackupIntentForFilesystem expression: TmpStatus
[gle=0x80004005]
2018-04-01 01:23:18, Error CSI 0000024b (F) STATUS_ACCESS_DENIED #3464940# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = 0, handle = {provider=NULL, handle=0}, da = (FILE_GENERIC_READ|DELETE), oa = @0x111e510->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[102]"\SystemRoot\WinSxS\Temp\9fd42bde3ec9d301e7000000381a781b\bb8477de3ec9d3012f010000381a781b_wmplayer.exe"; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0x111e5c0, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000022]
2018-04-01 01:23:18, Error CSI 0000024c@2018/3/31:22:23:18.169 (F) d:\w7rtm\base\wcp\sil\merged\ntu\ntsystem.cpp(2057): Error STATUS_ACCESS_DENIED originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2018-04-01 01:23:18, Error CSI 0000024d (F) STATUS_ACCESS_DENIED #3464939# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingFile(...)[gle=0xd0000022]
2018-04-01 01:23:18, Error CSI 0000024e (F) STATUS_ACCESS_DENIED #3464938# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingFile(flags = 0, da = (FILE_GENERIC_READ|DELETE), oa = @0x111eb60->SIL_OBJECT_ATTRIBUTES {s:40; on:"bb8477de3ec9d3012f010000381a781b_wmplayer.exe"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_SYNCHRONOUS_IO_NONALERT|FILE_NON_DIRECTORY_FILE|FILE_OPEN_FOR_BACKUP_INTENT), file = NULL, disp = (null))
[gle=0xd0000022]
2018-04-01 01:23:18, Error CSI 0000024f (F) HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED) #3462940# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x80070005]
2018-04-01 01:23:18, Error CSI 00000250 (F) HRESULT_FROM_WIN32(ERROR_ACCESS_DENIED) #3453940# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_AddFiles(Flags = 1, a = @0x237f120, fn = @0x237f920, fp = @0x2380120, disp = 0, op = 0)[gle=0x80070005]
2018-04-01 01:23:18, Info CBS Failed to add to transaction package: Package_1242_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2 [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-04-01 01:23:18, Error CBS Failed to stage execution package: Package_1242_for_KB4054518~31bf3856ad364e35~amd64~~6.1.1.2 [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-04-01 01:23:18, Info CSI 00000251@2018/3/31:22:23:18.213 CSI Transaction @0x9415770 destroyed
2018-04-01 01:23:18, Info CBS Perf: Stage chain complete.
2018-04-01 01:23:18, Info CBS Failed to stage execution chain. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-04-01 01:23:18, Error CBS Failed to process single phase execution. [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-04-01 01:23:18, Info CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.23964.1.2, status: 0x80070005, failure source: Stage, start state: Resolved, target state: Installed, client id: WindowsUpdateAgent
2018-04-01 01:23:18, Info CBS Failed to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-04-01 01:23:18, Info CBS Failed to add %windir%\winsxs\pending.xml to WER report because it is missing. Continuing without it...
2018-04-01 01:23:18, Info CBS Failed to add %windir%\winsxs\pending.xml.bad to WER report because it is missing. Continuing without it...
2018-04-01 01:23:18, Info CBS Reboot mark refs: 0
2018-04-01 01:23:18, Info CBS SQM: Reporting package change for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.23964.1.2, current: Resolved, pending: Default, start: Resolved, applicable: Installed, target: Installed, limit: Installed, hotpatch status: StillGoing, status: 0x0, failure source: Stage, reboot required: False, client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 1137, first merged sequence: 1137
2018-04-01 01:23:18, Info CBS SQM: Upload requested for report: PackageChangeBegin_Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.23964.1.2, session id: 142859, sample type: Standard
2018-04-01 01:23:18, Info CBS SQM: Ignoring upload request because the sample type is not enabled: Standard
2018-04-01 01:23:18, Info CBS SQM: Reporting package change completion for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.23964.1.2, current: Resolved, original: Resolved, target: Installed, status: 0x80070005, failure source: Stage, failure details: "(null)", client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 1137, first merged sequence: 1137
2018-04-01 01:23:18, Info CBS SQM: stage time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2018-04-01 01:23:18, Info CBS SQM: execute time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2018-04-01 01:23:18, Info CBS SQM: Upload requested for report: PackageChangeEnd_Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.23964.1.2, session id: 142862, sample type: Standard
2018-04-01 01:23:18, Info CBS SQM: Ignoring upload request because the sample type is not enabled: Standard
2018-04-01 01:23:18, Info CBS Enabling LKG boot option
2018-04-01 01:23:18, Info CBS Exec: End: nested restore point - complete.
2018-04-01 01:23:18, Info CBS Restored system sleep block state: 0x80000000
2018-04-01 01:23:18, Info CBS Exec: Processing complete. Session: 30656830_3598567061, Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.23964.1.2 [HRESULT = 0x80070005 - E_ACCESSDENIED]
2018-04-01 01:33:18, Info CBS Reboot mark refs incremented to: 1
2018-04-01 01:33:18, Info CBS Scavenge: Starts
 

Attachments

Yes, thank you, still cannot install this update. Tried almost everything - dsim, sfc, installing and uninstalling different updates-no success. One thing I could go a step forward is to make sfc work and now sfc \scan tells than everything is ok, and no errors.
Below, is my last update log. Cannot understand where to find error in permissions.
 

Attachments

BrianDrab said:
Do you happen to have a Logitech Gaming mouse attached to this computer?
Click to expand...
Yes, I do. Mouse, keyboard and gaming pad. All Logitech. Tried to exit Logitech software, than removed mouse(receiver) from computer, then run update.Still have a error. April security update failed with the same error, thought KB890830 installed succesfully. System is free from viruses - scanned it from boot cd, firewall is disabled and all services are stopped.
 
Are you able to uninstall the Logitech Software from your computer so that you are not using the mouse or software/drivers at all. Then attempt KB4054518 again and if it fails provide the CBS.log and setupapi.dev.log again?
 
BrianDrab said:
Are you able to uninstall the Logitech Software from your computer so that you are not using the mouse or software/drivers at all. Then attempt KB4054518 again and if it fails provide the CBS.log and setupapi.dev.log again?
Click to expand...
Removed logitech drivers, removed mouse. No success.
 

Attachments

Removing the mouse actually helped me identify the issue. Please start with the following. Please note that your machine will reboot during the fix so plan accordingly.

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop. You can use the one you already have downloaded.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

Please do the following.

FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download attached file and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
 

Attachments

This does not help.
Thank you for your help, it seems that to reinstall it - will be the easiest way to solve this problem. Copy files and wipe disk. Install again. It is the way i use to solve the problems with windows since Win95. I should not turn from this way.
I think it can be closed now.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top