Failed to start upload with file pattern c windows servicing sqm

Sysnative Forums

Картинка с сайта: www.sysnative.com

  • Still running Windows 7 or earlier? Support for Windows 7 ended on January 14th 2020. Please review the thread here for more details.

  • Microsoft Support & Malware Removal

  • Windows 7 | Windows Vista

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

[SOLVED] SQM error messages in CBS.log

  • Thread starter
    Thread starter

    mike1950r

  • Start date
    Start date

Joined
Oct 21, 2017
Posts
168




  • #1

Hi,

we find in every of our computers (windows7 64bit)
in cbs.log following lines concerning SQM:

CBS SQM: Initializing online with Windows opt-in: False
CBS SQM: Cleaning up report files older than 10 days.
CBS SQM: Requesting upload of all unsent reports.
CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 — E_FAIL]
CBS SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 — E_FAIL]
CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
CBS SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 — E_FAIL]

we would be very glad if someone could bring some more light into this issue.

thanks in advance

cheers mike

Joined
Oct 9, 2014
Posts
741




  • #2

Hi!

That’s normal as it’s present in every log and nothing to be worried about as long as SURT and SFC are clean and Windows Updates are working.

Joined
Oct 21, 2017
Posts
168




  • #3

Hi softwaremaniac,

nice to hear from you again.

I have no errors in SFC and Windows Update is working.
BTW I cannot find any SURT file in CBS folder.

Cheers mike

Joined
Oct 9, 2014
Posts
741




  • #4

SURT is a tool (System Update Readiness) which leaves CheckSUR.log in that folder after its run.

Joined
Oct 21, 2017
Posts
168




  • #5

thanks for the info.

cheers mike

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

  • Microsoft Support & Malware Removal

  • Windows 7 | Windows Vista

Источник

Tried updating with march preview, same error; I see other entries like: CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard; what is microsoft trying to upload to what?  «

CBS    SQM: Upload requested for report: PackageChangeEnd_Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24058.1.5, session id: 142862, sample type: Standard
CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard»

«Sample type»? for what?

Microsoft-Windows-SMBMiniRdr, Version = 6.1.7601.24024, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad3
2018-03-03 05:12:09, Info                  CSI    64e35}, Type neutral, TypeName neutral, PublicKey neutral
    Microsoft-Windows-SMBMiniRdr, Version = 6.1.7601.23915, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    Microsoft-Windows-QoS, Version = 6.1.7601.24000, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    Microsoft-Windows-QoS, Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    Microsoft-Windows-exFAT, Version = 6.1.7601.23717, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
    Microsoft-Windows-exFAT, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2018-03-03 05:12:12, Info                  CSI    000000ff@2018/3/3:12:12:12.487 CSI perf trace:
CSIPERF:TXCOMMIT;199124
CBS    Startup: Primitive operations were successfully rolled back.
CBS    Setting RollbackFailed flag to 1
Error                 CBS    Startup: Rollback failed, startupPhase: 0. [HRESULT = 0x80004005 — E_FAIL]
CBS    Setting ExecuteState key to: CbsExecuteStateFailed
CBS    Doqe: Enabling Device installs
CSI    00000100 Cancelling transactions: [1:[85]»TI4.30651110_520159795:4/Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24058.1.5″[1]»]»

CSI    00000101 Creating NT transaction (seq 3), objectname [6]»(null)»
CSI    00000102 Created NT transaction (seq 3) result 0x00000000, handle @0x25c
CSI    00000103@2018/3/3:12:12:15.092 CSI perf trace:
CSIPERF:TXCOMMIT;336203
CBS    Clearing HangDetect value
CBS    Saved last global progress. Current: 1, Limit: 1, ExecuteState: CbsExecuteStateFailed
CBS    Doqe: Unlocking driver updates, Count 4
CBS    WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24058.1.5, status: 0x80004005, failure source: GC, start state: Staged, target state: Installed, client id: WindowsUpdateAgent
CBS    Failed to query DisableWerReporting flag.  Assuming not set… [HRESULT = 0x80070002 — ERROR_FILE_NOT_FOUND]
CBS    Failed to add %windir%\winsxs\pending.xml to WER report because it is missing.  Continuing without it…
CBS    Failed to add %windir%\winsxs\pending.xml.bad to WER report because it is missing.  Continuing without it…
CBS    SQM: Reporting package change completion for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24058.1.5, current: Installed Invalid, original: Staged, target: Installed, status: 0x80004005, failure source: GC, failure details: «80004005   netsh.exe   1   24   Uninstall (upgrade)   Microsoft-Windows-PeerDist, Culture=neutral, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS   «, client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 1687, first merged sequence: 1687
CBS    SQM: Upload requested for report: PackageChangeEnd_Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24058.1.5, session id: 142862, sample type: Standard

Note: CBS    SQM: Upload requested for report: PackageChangeEnd_Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24058.1.5, session id: 142862, sample type: Standard

session id: 142862

Shadow Remote control configuration. This value becomes effective only if you set the fInheritShadow flag to 0.
0: Deny remote control.
1: Obtain user permission and interact with the session.
2: Do not obtain user permission and interact with the session.
3: Obtain user permission and display session.
4: Do not obtain user permission and display session.

Disable Remote Control of Terminal Server
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\DefaultUserConfiguration]
«fInheritShadow»=dword:00000000
«Shadow»=dword:00000000
«fInheritAutoLogon»=dword:00000000
«fInheritInitialProgram»=dword:00000000
«fLogonDisabled»=dword:00000001

Could there be a correlation?

or possibly this:

018-03-02 02:43:54, Info                  CBS    SQM: Initializing online with Windows opt-in: False
2018-03-02 02:43:54, Info                  CBS    SQM: Cleaning up report files older than 10 days.
2018-03-02 02:43:54, Info                  CBS    SQM: Requesting upload of all unsent reports.
2018-03-02 02:43:54, Info                  CBS    SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 — E_FAIL]
2018-03-02 02:43:54, Info                  CBS    SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 — E_FAIL]
2018-03-02 02:43:54, Info                  CBS    SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2018-03-02 02:43:54, Info                  CBS    SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 — E_FAIL]

with this:

How to stop Microsoft from gathering telemetry data from Windows 7, 8, and 8.1
https://superuser.com/questions/972501/how-to-stop-microsoft-from-gathering-telemetry-data-from-windows-7-8-and-8-1#972506

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Channels\Microsoft-Windows-Application-Experience/Program-Telemetry]
«Enabled»=dword:00000000

Источник

    Hello, I have Windows 7 Ultimate 64 bits and for a long time now I can’t update it, I have tried different methods and I can’t get it to update, the error codes that appear are the following:

    800B0109
    8007064A
    9C48

    And they refer to trying to install certain updates that are never installed and the same result is always recurring. Additionally, I have detected that in the installed updates, none of Microsoft Windows appears, just as if I try to activate or deactivate windows features, it appears blank.

    in the CBS.log file I get:

    CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 – E_FAIL]

    And if I go to the folder C:\Windows\servicing\SQM

    it is blank.

    Thank you and waiting for you to give me some kind of help or advice about this update problem.

  2. Did you notice windows 7 is EOS/L for almost over 2 years now (i don’t see it mentioned)? Only by using the ESU Bypass tool you can still get updates on WU/manually installed, is it in use?.


    Stop hovering to collapse…
    Click to collapse…


    Hover to expand…
    Click to expand…

  3. true.
    also yes, it’s been 2 years already. 3 months until 3 years of eos + esu ending


    Stop hovering to collapse…
    Click to collapse…


    Hover to expand…
    Click to expand…

  4. Jan 20210 were the last pre-ESU updates.

    Getting old


    Stop hovering to collapse…
    Click to collapse…


    Hover to expand…
    Click to expand…

  5. you’re also right, because i’ve seen modern m$ updates (e.g. m$ edge being installed)
    i was assuming the official eol date
    why did m$ release those january 2021 updates anyway?
    this means i wonder, if the businesses with genuine/real esu (no bypass, true license) were issued those weird updates


    Stop hovering to collapse…
    Click to collapse…


    Hover to expand…
    Click to expand…

  6. I don’t have an ESU license and haven’t used any tools to bypass the ESU license, I’ll try that.

  7. Could always use Simplix Pack instead as it’s much more reliable than WU.

Источник

А как же второй вариант ?!

Добавлено через 24 минуты
Ладно,решил всё расписать. Вдруг понадобится тем,кто также столкнётся с схожей проблемой.
Вот инфа из CBS.log:

Кликните здесь для просмотра всего текста

2017-08-04 15:23:34, Info CBS Starting TrustedInstaller initialization.
2017-08-04 15:23:34, Info CBS Loaded Servicing Stack v6.1.7601.18766 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601 .18766_none_675144b3de10d6f7\cbscore.dll
2017-08-04 15:23:34, Info CSI 00000001@2017/8/4:12:23:34.958 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fed816f0dd @0x7fed91c98b5 @0x7fed91934e3 @0xff0ae97c @0xff0ad799 @0xff0adb2f)
2017-08-04 15:23:34, Info CSI 00000002@2017/8/4:12:23:34.975 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fed816f0dd @0x7fed9216816 @0x7fed91e2b18 @0x7fed91935b9 @0xff0ae97c @0xff0ad799)
2017-08-04 15:23:34, Info CSI 00000003@2017/8/4:12:23:34.976 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fed816f0dd @0x7fefa518738 @0x7fefa518866 @0xff0ae474 @0xff0ad7de @0xff0adb2f)
2017-08-04 15:23:34, Info CBS Ending TrustedInstaller initialization.
2017-08-04 15:23:34, Info CBS Starting the TrustedInstaller main loop.
2017-08-04 15:23:34, Info CBS TrustedInstaller service starts successfully.
2017-08-04 15:23:34, Info CBS SQM: Initializing online with Windows opt-in: False
2017-08-04 15:23:34, Info CBS SQM: Cleaning up report files older than 10 days.
2017-08-04 15:23:34, Info CBS SQM: Requesting upload of all unsent reports.
2017-08-04 15:23:34, Info CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 — E_FAIL]
2017-08-04 15:23:34, Info CBS SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 — E_FAIL]
2017-08-04 15:23:34, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2017-08-04 15:23:34, Info CBS SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 — E_FAIL]
2017-08-04 15:23:34, Info CBS Blocked system sleep; prior state: 0x80000000
2017-08-04 15:23:34, Info CSI 00000004 CSI Store 4094560 (0x00000000003e7a60) initialized
2017-08-04 15:23:34, Info CBS Session: 30596827_1538141926 initialized by client WindowsUpdateAgent.
2017-08-04 15:23:34, Info CBS Startup: current ExecuteState is CbsExecuteStateResolvePending | CbsExecuteStateFlagRollback
2017-08-04 15:23:34, Info CBS Disabling LKG boot option
2017-08-04 15:23:34, Info CBS Startup: Initializing driver operations queue.
2017-08-04 15:23:34, Info CBS Startup: Initializing advanced operation queue.
2017-08-04 15:23:34, Info CBS Startup: Waiting for SC autostart event
2017-08-04 15:23:34, Info CBS Startup: SC autostart event signaled
2017-08-04 15:23:35, Info CBS Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Rollback.
2017-08-04 15:23:35, Info CBS Startup: Processing advanced operation queue, startupPhase: 0
2017-08-04 15:23:35, Info CSI 00000005 IAdvancedInstallerAwareStore_ResolvePend ingTransactions (call 1) (flags = 0000000a, progress = NULL, phase = 0, pdwDisposition = @0x19cfd70
2017-08-04 15:23:35, Info CSI 00000006 IAdvancedInstallerAwareStore_ResolvePend ingTransactions call 1 loaded 12 (0x000000000000000c) pending advanced installer operations
2017-08-04 15:23:35, Info CSI 00000007 Begin executing advanced installer phase 8 index 0 (sequence 0)
Old component: [l:0]»»
New component: [l:0]»»
Install mode: uninstall
Installer ID: {51d813ef-83f1-42de-a2ee-89ee4633a7c9}
Installer name: [25]»RegistryKey SD Applicator»
2017-08-04 15:23:35, Info CSI 00000008 End executing advanced installer (sequence 0)
Completion status: S_OK

2017-08-04 15:23:35, Info CSI 00000009 Begin executing advanced installer phase 10 (0x0000000a) index 0 (sequence 0)
Old component: [l:0]»»
New component: [l:0]»»
Install mode: install
Installer ID: {51d813ef-83f1-42de-a2ee-89ee4633a7c9}
Installer name: [25]»RegistryKey SD Applicator»
2017-08-04 15:23:35, Info CSI 0000000a End executing advanced installer (sequence 0)
Completion status: S_OK

2017-08-04 15:23:35, Info CSI 0000000b Begin executing advanced installer phase 22 (0x00000016) index 22 (0x0000000000000016) (sequence 45)
Old component: [ml:296{148},l:294{147}]»Microsoft-Windows-AppID, Culture=neutral, Version=6.1.7601.23677, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS»
New component: [ml:296{148},l:294{147}]»Microsoft-Windows-AppID, Culture=neutral, Version=6.1.7601.19021, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS»
Install mode: uninstall
Installer ID: {1b265fd2-721c-4e59-ad55-9d102a5d1d7f}
Installer name: [12]»SppInstaller»
2017-08-04 15:23:35, Info CSI 0000000c Performing 1 operations; 1 are not lock/unlock and follow:
LockComponentPath (10): flags: 0 comp: {l:16 b:48c52f7e1c0dd301010000008c17681e} pathid: {l:16 b:48c52f7e1c0dd301020000008c17681e} path: [l:204{102}]»\SystemRoot\WinSxS\amd64_microsoft-windows-appid_31bf3856ad364e35_6.1.7601.23677_no ne_b5bda64be2129cfe» pid: 178c starttime: 131463230148935546 (0x01d30d1c7e0d7f7a)
2017-08-04 15:23:35, Info CSI 0000000d Performing 1 operations; 1 are not lock/unlock and follow:
LockComponentPath (10): flags: 0 comp: {l:16 b:0484307e1c0dd301030000008c17681e} pathid: {l:16 b:0484307e1c0dd301040000008c17681e} path: [l:204{102}]»\SystemRoot\WinSxS\amd64_microsoft-windows-appid_31bf3856ad364e35_6.1.7601.19021_no ne_b5640de2c8d1e7b2″ pid: 178c starttime: 131463230148935546 (0x01d30d1c7e0d7f7a)
2017-08-04 15:23:35, Info CSI 0000000e Performing 1 operations; 1 are not lock/unlock and follow:
LockComponentPath (10): flags: 0 comp: {l:16 b:22b0347e1c0dd301050000008c17681e} pathid: {l:16 b:22b0347e1c0dd301060000008c17681e} path: [l:238{119}]»\SystemRoot\WinSxS\amd64_microsoft-windows-security-spp-installer_31bf3856ad364e35_6.1.7600.1638 5_none_12cbc2d3c1ed26ee» pid: 178c starttime: 131463230148935546 (0x01d30d1c7e0d7f7a)
2017-08-04 15:23:35, Info CSI 0000000f@2017/8/4:12:23:35.160 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{1b265fd2-721c-4e59-ad55-9d102a5d1d7f};Microsoft-Windows-AppID, Version = 6.1.7601.19021, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;51213
2017-08-04 15:23:35, Info CSI 00000010 End executing advanced installer (sequence 45)
Completion status: S_OK

2017-08-04 15:23:35, Info CSI 00000011 Begin executing advanced installer phase 24 (0x00000018) index 23 (0x0000000000000017) (sequence 48)
Old component: [ml:296{148},l:294{147}]»Microsoft-Windows-AppID, Culture=neutral, Version=6.1.7601.23677, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS»
New component: [ml:296{148},l:294{147}]»Microsoft-Windows-AppID, Culture=neutral, Version=6.1.7601.19021, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS»
Install mode: uninstall
Installer ID: {1b265fd2-721c-4e59-ad55-9d102a5d1d7f}
Installer name: [12]»SppInstaller»
2017-08-04 15:23:35, Info CSI 00000012@2017/8/4:12:23:35.166 CSI Advanced installer perf trace:
CSIPERF:AIDONE;{1b265fd2-721c-4e59-ad55-9d102a5d1d7f};Microsoft-Windows-AppID, Version = 6.1.7601.19021, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;6810
2017-08-04 15:23:35, Info CSI 00000013 End executing advanced installer (sequence 48)
Completion status: S_OK

2017-08-04 15:23:35, Info CSI 00000014 Begin executing advanced installer phase 24 (0x00000018) index 24 (0x0000000000000018) (sequence 49)
Old component: [ml:292{146},l:290{145}]»Microsoft-Windows-LSA, Culture=neutral, Version=6.1.7601.23677, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=wow64, versionScope=NonSxS»
New component: [ml:292{146},l:290{145}]»Microsoft-Windows-LSA, Culture=neutral, Version=6.1.7601.19160, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=wow64, versionScope=NonSxS»
Install mode: uninstall
Installer ID: {3bb9fd2b-351e-4b9c-b1fc-ed0758805998}
Installer name: [6]»Events»
2017-08-04 15:23:35, Info CSI 00000015 Performing 1 operations; 1 are not lock/unlock and follow:
LockComponentPath (10): flags: 0 comp: {l:16 b:c75e377e1c0dd301070000008c17681e} pathid: {l:16 b:c75e377e1c0dd301080000008c17681e} path: [l:200{100}]»\SystemRoot\WinSxS\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.23677_none _0f10cb14c1174b29″ pid: 178c starttime: 131463230148935546 (0x01d30d1c7e0d7f7a)
2017-08-04 15:23:35, Info CSI 00000016 Performing 1 operations; 1 are not lock/unlock and follow:
LockComponentPath (10): flags: 0 comp: {l:16 b:a943387e1c0dd301090000008c17681e} pathid: {l:16 b:a943387e1c0dd3010a0000008c17681e} path: [l:200{100}]»\SystemRoot\WinSxS\wow64_microsoft-windows-lsa_31bf3856ad364e35_6.1.7601.19160_none _0e8af497a7f7e971″ pid: 178c starttime: 131463230148935546 (0x01d30d1c7e0d7f7a)
2017-08-04 15:23:35, Info CSI 00000017 Performing 1 operations; 1 are not lock/unlock and follow:
LockComponentPath (10): flags: 0 comp: {l:16 b:f3a03d7e1c0dd3010b0000008c17681e} pathid: {l:16 b:f3a03d7e1c0dd3010c0000008c17681e} path: [l:220{110}]»\SystemRoot\WinSxS\amd64_microsoft-windows-wmi-cmiplugin_31bf3856ad364e35_6.1.7601.1751 4_none_1b28925642a756f7″ pid: 178c starttime: 131463230148935546 (0x01d30d1c7e0d7f7a)

Как видно запуск службы проходит успешно. И после запуска «система» начинает что-то удалять и заново устанавливать. А судя по логу Process Monitor после этих действий процесс TrustedInstaller.exe аварийно завершается.

Обратите внимание на эти операции. Система проводит операцию uninstall для системных компонентов Microsoft-Windows-AppID и Microsoft-Windows-LSA. Примечательны версии этих компонентов.

6.1.7601.23677 — принадлежит обновлению KB4012212.
Так что,выдвигаю предположение — система (с помощью службы TrustedInstaller) пытается удалить обновление KB4012212,но у неё не выходит. Возможно как раз таки из-за повреждения хранилища.

Добавлено через 1 минуту
Почему система сразу начинает выполнять эти операции после запуска службы (не полного,служба,так сказать,не до конца запустилась) я не знаю.

Добавлено через 52 секунды
В общем жду

Сообщение от Turok123

checksur.log

Добавлено через 38 минут
Кстати. Вот подтверждение мой теории. Все эти действия вызваны WindowsUpdateAgent.

Сообщение от Turok123

2017-08-04 15:23:34, Info CBS Session: 30596827_1538141926 initialized by client WindowsUpdateAgent.

Сообщение от Turok123

2017-08-04 15:23:35, Info CBS Progress: UI message updated. Operation type: Update. Stage: 1 out of 1. Rollback.

Источник

Понравилась статья? Поделить с друзьями:
0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии
  • Самый надежный ноутбук на windows
  • Как посмотреть частоту оперативной памяти на windows 10 через командную строку
  • Драйвер для canon imagerunner 1133 windows 10
  • Как подключить 2 монитора к одному компьютеру windows 10 через hdmi
  • Windows forms data binding