Question about code integrity

did a clean installation of windows 11 and looked into the event manager and found that event:

Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Windows\System32\fcon.dll because the set of per-page image hashes could not be found on the system.

is that normal?
sfc scan finds no issues

Windows 11 22621.1778
Windows Feature Experience Pack 1000.22642.1000.0
Ryzen 7900x
670E Steel Legend

Jheezy said:

did a clean installation of windows 11 and looked into the event manager and found that event:

Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume3\Windows\System32\fcon.dll because the set of per-page image hashes could not be found on the system.

is that normal?
sfc scan finds no issues

Windows 11 22621.1778
Windows Feature Experience Pack 1000.22642.1000.0
Ryzen 7900x
670E Steel Legend

Click to expand...

I think I have the same error on my computers even after a clean install. Let me double check and get back to you.
Do you remember the event ID?


Edit:
Seems like malwarebytes also includes this information on every scan. Googling this error message gives alot of results.
Also, the same error-message appears in this thread:

If you scroll down you see the following:
"CodeIntegrity:
===============
Date: 2023-06-06 12:47:44
Description:
Code Integrity is unable to verify the image integrity of the file \Device\HarddiskVolume8\Windows\System32\fcon.dll because the set of per-page image hashes could not be found on the system. "


Probably nothing to worry about.

Looks like a new bug in Windows.

RJARRRPCGP said:

Looks like a new bug in Windows.

Click to expand...

Can't be too new since this thread is from June 2023.

pbcopter said:

Can't be too new since this thread is from June 2023.

Click to expand...

Think it's from a Windows update in 2023? That's not too long ago in Windows 11 terms. This error occurs randomly, from what I know. I don't remember seeing such until this year.
I just got this for a new event log entry this month, FFS!

I don't know why you believe that that Event log entry is worth investigating.
Event logs exist for Windows' benefit not ours.

Event log entries can help us investigate problems for which there are behavioural symptoms but the mere existence of Event log entries is not a sufficient reason to initiate an investigation.


All the best,
Denis