Solved Cannot create task in Task Scheduler

Try3 · Jul 23, 2023

The SFC tutorial tells you [in the notes at the end of Option 1] what to do if SFC reports irreparable errors.

The SFC tutorial [Option 3] tells you how to extract the relevant lines from the CBS log.
That extraction should be short enough to post here.

And don't forget the test in another user account. It can identify problems that SFC cannot.

All the best,
Denis

PilgrimLyieu · Jul 23, 2023

Try3 said:
The SFC tutorial tells you [in the notes at the end of Option 1] what to do if SFC reports irreparable errors.

The SFC tutorial [Option 3] tells you how to extract the relevant lines from the CBS log.
That extraction should be short enough to post here.

And don't forget the test in another user account. It can identify problems that SFC cannot.

All the best,
Denis

2023-07-23 19:45:49, Info CSI 0000017d [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 19:45:51, Info CSI 00000181 [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 19:45:51, Info CSI 00000182 [SR] This component was referenced by [l:114]'Microsoft-Client-Features-Classic-Package~31bf3856ad364e35~amd64~~10.0.22621.1825.c0a69d0baca859a2af1ff6fb6dd334ac'
2023-07-23 19:45:51, Info CSI 00000185 [SR] Could not reproject corrupted file \??\C:\Windows\Web\Screen\\img105.jpg; source file in store is also corrupted

2023-07-23 19:47:10, Info CSI 000002af [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 19:47:10, Info CSI 000002b1 [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 19:47:10, Info CSI 000002b2 [SR] This component was referenced by [l:114]'Microsoft-Client-Features-Classic-Package~31bf3856ad364e35~amd64~~10.0.22621.1825.c0a69d0baca859a2af1ff6fb6dd334ac'
2023-07-23 19:47:10, Info CSI 000002b5 [SR] Could not reproject corrupted file \??\C:\Windows\Web\Screen\\img105.jpg; source file in store is also corrupted

2023-07-23 19:50:51, Info CSI 0000040d [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 19:50:52, Info CSI 00000410 [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 19:50:52, Info CSI 00000411 [SR] This component was referenced by [l:114]'Microsoft-Client-Features-Classic-Package~31bf3856ad364e35~amd64~~10.0.22621.1825.c0a69d0baca859a2af1ff6fb6dd334ac'
2023-07-23 19:50:52, Info CSI 00000414 [SR] Could not reproject corrupted file \??\C:\Windows\Web\Screen\\img105.jpg; source file in store is also corrupted

2023-07-23 19:52:04, Info CSI 0000053e [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 19:52:04, Info CSI 00000540 [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 19:52:04, Info CSI 00000541 [SR] This component was referenced by [l:114]'Microsoft-Client-Features-Classic-Package~31bf3856ad364e35~amd64~~10.0.22621.1825.c0a69d0baca859a2af1ff6fb6dd334ac'
2023-07-23 19:52:04, Info CSI 00000544 [SR] Could not reproject corrupted file \??\C:\Windows\Web\Screen\\img105.jpg; source file in store is also corrupted

2023-07-23 19:54:49, Info CSI 00000698 [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 19:54:50, Info CSI 0000069b [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 19:54:50, Info CSI 0000069c [SR] This component was referenced by [l:114]'Microsoft-Client-Features-Classic-Package~31bf3856ad364e35~amd64~~10.0.22621.1825.c0a69d0baca859a2af1ff6fb6dd334ac'
2023-07-23 19:54:50, Info CSI 0000069f [SR] Could not reproject corrupted file \??\C:\Windows\Web\Screen\\img105.jpg; source file in store is also corrupted

2023-07-23 19:56:01, Info CSI 000007c9 [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 19:56:01, Info CSI 000007cb [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 19:56:01, Info CSI 000007cc [SR] This component was referenced by [l:114]'Microsoft-Client-Features-Classic-Package~31bf3856ad364e35~amd64~~10.0.22621.1825.c0a69d0baca859a2af1ff6fb6dd334ac'
2023-07-23 19:56:01, Info CSI 000007cf [SR] Could not reproject corrupted file \??\C:\Windows\Web\Screen\\img105.jpg; source file in store is also corrupted

2023-07-23 20:03:11, Info CSI 00000926 [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 20:03:12, Info CSI 00000929 [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 20:03:12, Info CSI 0000092a [SR] This component was referenced by [l:114]'Microsoft-Client-Features-Classic-Package~31bf3856ad364e35~amd64~~10.0.22621.1825.c0a69d0baca859a2af1ff6fb6dd334ac'
2023-07-23 20:03:12, Info CSI 0000092d [SR] Could not reproject corrupted file \??\C:\Windows\Web\Screen\\img105.jpg; source file in store is also corrupted

2023-07-23 20:04:25, Info CSI 00000a57 [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 20:04:25, Info CSI 00000a59 [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 20:04:25, Info CSI 00000a5a [SR] This component was referenced by [l:114]'Microsoft-Client-Features-Classic-Package~31bf3856ad364e35~amd64~~10.0.22621.1825.c0a69d0baca859a2af1ff6fb6dd334ac'
2023-07-23 20:04:25, Info CSI 00000a5d [SR] Could not reproject corrupted file \??\C:\Windows\Web\Screen\\img105.jpg; source file in store is also corrupted

Here are some lines in sfcdetails.txt with "Cannot repair member file ...". Does it mean anything? And what should I do then?

Try3 · Jul 23, 2023

PilgrimLyieu said:
what should I do then?

Try3 said:
The SFC tutorial tells you [in the notes at the end of Option 1] what to do if SFC reports irreparable errors.

That.

Best of luck,
Denis

PilgrimLyieu · Jul 23, 2023

Try3 said:
And don't forget the test in another user account. It can identify problems that SFC cannot.

The new account (both standard account and administrator account) meats the same issue.

Try3 · Jul 23, 2023

PilgrimLyieu said:
The new account (both standard account and administrator account) meats the same issue.

In that case, pursue the irreparable SFC faults and, if that does not fix things, run a Repair install.

Try3 said:
The SFC tutorial tells you [in the notes at the end of Option 1] what to do if SFC reports irreparable errors.

All the best,
Denis

PilgrimLyieu · Jul 23, 2023

After several times restart, I get a sfcdetails.txt and its content no longer changes. Here's its "Cannot repair" line

2023-07-23 22:47:56, Info CSI 0000014f [SR] Beginning Verify and Repair transaction
2023-07-23 22:47:56, Info CSI 00000151 [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 22:47:57, Info CSI 00000154 [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 22:47:57, Info CSI 00000155 [SR] This component was referenced by [l:114]'Microsoft-Client-Features-Classic-Package~31bf3856ad364e35~amd64~~10.0.22621.1825.c0a69d0baca859a2af1ff6fb6dd334ac'
2023-07-23 22:47:57, Info CSI 00000158 [SR] Could not reproject corrupted file \??\C:\Windows\Web\Screen\\img105.jpg; source file in store is also corrupted
2023-07-23 22:47:57, Info CSI 00000159 [SR] Verify complete

2023-07-23 22:49:06, Info CSI 00000280 [SR] Beginning Verify and Repair transaction
2023-07-23 22:49:06, Info CSI 00000282 [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 22:49:06, Info CSI 00000284 [SR] Cannot repair member file [l:10]'img105.jpg' of Microsoft-Windows-ThemeUI-LockscreenBackgrounds-Client, version 10.0.22621.1, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, hash mismatch
2023-07-23 22:49:06, Info CSI 00000285 [SR] This component was referenced by [l:114]'Microsoft-Client-Features-Classic-Package~31bf3856ad364e35~amd64~~10.0.22621.1825.c0a69d0baca859a2af1ff6fb6dd334ac'
2023-07-23 22:49:06, Info CSI 00000288 [SR] Could not reproject corrupted file \??\C:\Windows\Web\Screen\\img105.jpg; source file in store is also corrupted
2023-07-23 22:49:06, Info CSI 00000289 [SR] Repair complete

I don't know what do they mean. But I found the file img105.jpg a lock screen background.

Does it truly matter?
And I've run Dism /Online /Cleanup-Image /RestoreHealth but it said healthy. Then I retried (to create a task) but failed again.
Should I continue the step to "do a system restore", "repair install" and "reset" further?
But I can't find "Fix problems using Windows Update"(Repair Install).

Try3 · Jul 23, 2023

You ran that Dism command given in the yellow-background notes of Option 1 of the SFC tutorial whilst connected to the internet?
If so then a Repair install is your only remaining hope.

If that img105.jpg was the only fault then I'd say just delete it but I would expect that Dism command to fix it anyway.
It's been many years since I've seen SFC include a check of such a ridiculous file.
I think it was a decade ago when it used to check a file was still in its original state despite the fact that another part of Windows used to write to it quite routinely.

Best of luck,
Denis

PilgrimLyieu · Jul 23, 2023

Try3 said:
You ran that Dism command given in the yellow-background notes of Option 1 of the SFC tutorial whilst connected to the internet?

Yes, with internet connected.

Try3 said:
If so then a Repair install is your only remaining hope.

Is my problem related to this?

I'm going crazy. :tears:

Try3 · Jul 23, 2023

PilgrimLyieu said:
Is my problem related to this?

Well, you have a fault in Windows and SFC has not fixed it.
A Repair install is nothing to be feared. I have used that procedure for every Version update for almost a decade.

Denis

PilgrimLyieu · Jul 23, 2023

But in Option One I can't find "Fix problems using Windows Update" in Repair Install Windows 11 with an In-place Upgrade. Should I try Option Two?

Try3 · Jul 23, 2023

Use Option 2.

[Option 1 is not yet relevant. As it says, it is there ready for Versions that only those in the test programme can use at the moment.]

Denis

PilgrimLyieu · Jul 23, 2023

Try3 said:
Use Option 2.

[Option 1 is not yet relevant. As it says, it is there ready for Versions that only those in the test programme can use at the moment.]

Denis

Thanks. The time is too late for me now(though I've stayed up late for this issue for days) and I'd like to continue to solve it tomorrow. Last questions today.

- I'm in version 23H2 22631.2048 with Windows Insider Program(beta channel), and the tutorial writes "The Windows 11 installation media (ISO or USB) must be the same edition, same version, and same or higher build as the currently installed Windows 11". Does it mean that I should use Windows Insider Program(beta channel) instead of stable release version to repair install?
- Should I backup my data? If so, what should I do?
- Will my Windows and Office activations disappear?

I'm sorry that these questions seem silly but I'm a true new hand.

Try3 · Jul 23, 2023

Yes, backup your data before any major operation.
Yes, make a new system image before any major operation.
No, activations, your installed applications, your own files & almost all Settings are not affected by a Repair install.

Yes, you need to use that Insider programme ISO.
Seek advice in whatever the ElevenForums News page is for your Insider programme Version. Search for 23H2 in titles-only to find it.

Denis

PilgrimLyieu · Jul 24, 2023

Today I updated to 23H2 22631.2050 and I found I could use Dism /Online /Cleanup-Image /RestoreHealth to repair. Then result of sfc /scannow turned to normal. So the results of both SFC and Dism are normal now.
And I restart computer again and try to create task, still fail. And I didn't continue to do a repair install since SFC and Dism are normal now.
Besides, here is something weird too I found. I've installed PowerToys the other day but I can not let it run at startup. Here's a GIF showing it.

In the GIF, I first ran PowerToys(not as Administrator) and opened the setting. Then I switched on the option "Run at startup" and exited PowerToys. And I ran PowerToys again(not as Administrator) but only to find the option still not turned on.
And I try to do this as Administrator and turn on the option "Always run as Administrator". However the issue still exists.

It's even weirder that sometimes it can work(I'm trying to find out in what cases) and I find that It created a task in Task Scheduler to run at startup. As a result, I think this has something to do with this topic. Hope this will give you some insight.

PilgrimLyieu · Jul 24, 2023

Solution

Hello everyone who are following this thread. I think I've found where the issue lies in. This issue mainly occurs on (Chinese) users who use Huorong, a popular and wide-used Chinese anti-virus software.
I've turned on the option "系统任务目录 - 保护系统任务目录不被篡改"(System task directory - to protect the system task directory from being tampered with) in "系统防护 > 系统加固 > 文件防护"(System Protection > System Hardening > File Protection).

Then when some progresses try to create a task, I would be asked if I know and allow.

Then, maybe I checked the "Remember ..." box by accident in one time and chose "Prevent". And this operation was remembered in "自动处理"(Automatic Processing).

Now I've removed this rule and everything goes well now.
Finally, thanks all people giving me hands in the thread. And I share my experience and solution to people having the possibility to meet the issue.