There are several know issues with 2004. When those conditions are detected Microsoft blocks 2004 on those machines. You should absolutely not attempt a manual upgrade to 2004.

@Ramhound I understand, but I want to know what condition I'm hitting to see if it's something fixable. For example, if it's something I disabled using O&O ShutUp10, I could re-enable the setting. If it's an issue with my RAM, I could buy a different type of RAM that doesn't have the problem. I'm willing to fix the issue, I just need to know what it is.

O&O ShutUp 10 absolutely would be the culprit. I linked to the know issues, those issues indicate if it will block the upgrade, if and only if none of those issues are applicable can you feel safe to manually upgrade to 2004. Unfortunately, without know what options you enabled or disabled by using O&O ShutUp 10 it will be next to impossible for us to determine which setting is to blame. That program is know to make irreversible breaking changes to Windows 10 that causes all sorts of behavior. That message wouldn’t be caused by a memory incompatibility only hardware on the known issues.

Sorry, I should have been more clear in my question - I'm asking if there's a way to get the upgrader to tell me what condition it hit when it decided that computer is not eliglble. I'm not looking for someone on this website to tell me, I understand that it would be difficult (or impossible) to tell me the specific issue with only the information I've given

If your not looking for an answer I cannot really help.. I will again point out, it’s more likely a hardware block, if you upgrade to 2004 instead of simply waiting you will regret it. The logs for the upgrade assistance will actually indicate the reason. If you provide those logs to the community someone can tell you the reason your getting that message. This will be my last comment on the subject without those logs.

The answer I'm looking for would be the location of a log file or something similar that contains the answer I need. I'm willing to buy hardware that doesn't have the problem but I don't want to read through all the known issues to figure out which piece of hardware I have is the blocker.

BitLocker absolutely isn’t the reason for the hardware block.

I don't have bitlocker enabled, but thank you. Where are the logs? That is the answer I'm looking for

Logs. Please provide the necessary information to answer your question. Simply telling you where the logs are isn’t an acceptable answer. You might not be looking to be told the reason for the block but that is indeed the only acceptable answer (IMO)

Setup Diag in the past has also told me the reason a feature update failed to install. You should provide the relevant information from the logs.

I included the first logs. The CBS.log file is large enough that I'm having trouble finding a place to upload it to, but I'll add it in the next 20-30 minutes when I can find a place that will take it

Sources\Panther\CompatData_2020_06_28_15_27_24_3_006f0018.xm‌​l might contain a device identification number. You definitely have incompatible hardware. Your best solution is to simply wait for the block to be moved. Do you have any of the drivers Microsoft has indicated on your system?

Here is that file (also added to the question). I need this update for a feature in WSL2 (a build pipeline I use is broken on WSL classic), I am willing to replace the blocking hardware. Which log contains the drivers you are referring to? I will check.

I read through the file and I think the problems are laid out on lines 21 and 22. oem1.inf and oem2.inf have a value of "True" for BlockMigration. Is there a way to map that to a driver? I opened the file and it looks like an XPS Document Writer, but I don't have enough experience with drivers to know what that refers to.

You might not be able to replace the hardware. There is at least one hardware block that is soldered to your motherboard. Do you have any of those system files on your system? The logs don’t indicate the precise hardware just that it’s detected during the first phase (before or around 50%) in other words it’s not even getting to the phase where it attempts the installation. What are the contents of those two .inf files?

Location of oem1.inf and oem0.inf

OEM0: ghostbin.co/paste/tc6tv

OEM1: ghostbin.co/paste/n8ave

Ironically the article I linked to specifically indicates the solution those are both print drivers.

oh nice, thanks! I'll try removing them and seeing if that will help. Thanks again for all the help, I really appreciate how much effort you put into this specific, individual issue of mine

I would still advise waiting for the upgrade.

If these drivers aren't blocking me, how come? Wouldn't I have removed all the problems Microsoft can detect? My thinking is, if I hadn't had them installed to begin with, it would have worked without an error. Or is there something else I'm not considering?