I'm highly confident it is fixed.  

On the Manged Device, if you look on the Technical Application under inventory.....

When does it show the last time Inventory Started?  Completed?  Can you view the Inventory of the PC from there?

I ran the Inventory scan this morning from the managed device and yes I can see the inventory when clicking the "View Inventory Details" link. And scan time was updated with that info.

I also ran a Complete Inventory Scan on the device from ZCC an hour ago and scan time/date updated on the device from that too. But still getting blank page in ZCC for Detailed Hardware/Software Inventory. I have verified the processor is a 12th Gen Intel i5-12500 from This PC properties.

If it looks correct on the PC, then it is not the same issue as prior.......

I will look tomorrow for any known issues.

Try running "zac inv" with the Full Scan Parameter to see if that helps....just a guess until i dig deeper

I ran zac inv -f scannow and checked Tech Application to verify it worked but still no info on the Detailed Software/Hardware Inventory page. Almost like the link is broken, the blank page loads immediately.

And is that on the Device itself on the Technicians App?

I can also confirm that ALL 120 of my Dell Latitude 7430's, ALL 12 gen CPU's, have this problem. Most of them have a 20.3 agent. Both W11 and W10 so nothing better there.

I have unregistered the computers, cleared image safe data, re-registered with a new GUID, performed full scans. Inventory locally is fine and can be viewed with the link (viewInvFile.html)

All other models not based on a 12th Gen CPU are working correctly

BIOS is up to date or within a 1 version of being the latest, but updates to the BIOS have not resolved the problem.

I feel like this might have something to do with the Ecore feature of that CPU. I might try and limit the number of CPU's as a troubleshooting step.

One last thing, PRU's are up to date, and I can see the upload completed and is in the Success folder on the server.

Hopefully, it will be fixed in 23.4 due in Q4.  

There appear to be some XML escape issues around some data causing the issue.