The nvidia 340.xx legacy driver we embed should support the GeForce 9200 but it wouldn't be the first time that something on the edge of the driver support list doesn't work; i.e. really old cards that are on the trailing edge of the list.
SSH into the box and run "dmesg | paste" and "cat /var/log/Xorg.0.log | paste" and share the URL(s) here.
Fix has been merged. An 8.2.0.1 release will be made available sometime later tonight.
It's hard to comment without any information on the hardware you're using (including the GPU type, which is probably pertinent). Most times when people claim their box is frozen the OS is running fine and there is some other reason that graphics didn't start. If you know the IP address of the box try logging in and running "dmesg | paste" so we can see something about the boot.
Thread name updated so more people find it and read the above comment.
This is a known issue and it is the reason why we pulled the RPi/RPi2/Slice/Slice3 update files from our server about 12h ago. It is being investigated and there will be an 8.2.0.1 respin release once fixes are changed. No ETA at this time.
All images support PXE boot as long as you customise the boot process to PXE boot.
Maybe if you disable the onboard GPU and fit a newer alternative that's supported, but it's an ancient spec machine and a Raspberry Pi will deliver much better performance and use considerably less electricity.
that advise just restores the clean box to the same dirty state as when you did the backup #fail
take the backup, but DO NOT RESTORE IT
Instead extract/unpack the archive somewhere else and then stop Kodi (systemctl stop kodi) before selectively moving back the configuration items that you need. These are probably the guisettings.xml file, database files, and configuration in /storage/.kodi/userdata/addon_data/ - once done restart Kodi (systemctl start kodi) and rinse/repeat until things are back to normal.
Dell OptiPlex 740 Series Specs - CNET
Specs in the first link show either an NVS210 card or nForce 430. The first is not supported by either of the two nVidia drivers we currently embed and the second only lists Windows drivers under the legacy card section of the driver search app. Either way I think you have the answer.
It's not a 32-bit Linux version btw, because we dropped i386 builds ~3.5 years ago.
8.2.0 release files for RPi/RPi2 have been removed from the release/download server while cause and fix are investigated
The last 10+ releases of nvidia driver have noted some kind of "suspend fix" in documentation but it's never been the one that people have reported here so I wouldn't get hopes up.
I'd caution that nobody I'm aware of among staff uses PXE boot so there is ~zero testing done before releases, but as long as it continues to work there are no plans to remove or sabotage the feature.
What hardware and what version of OE are you updating from?
No debug log = no problem 
Hashes are worthless and are not the solution. We are working on a proper solution. Go poke in GitHub for more info.
I downloaded the driver from the link on the advert/listing but can only see references to using it on Android. It might compile on Linux but we don't have that driver in our images and honestly we have low/no desire to add more sh1t quality realtek drivers that are hard to maintain.
And I don't make hardware recommendations, sorry.
Realtek_RTL8812BU_USB_Module <= there are no known linux drivers for this chipset, so no it won't work
^ in this context "recognised" means the kernel can see there is a USB device attached, but because there is no driver in the kernel (because no driver exists for this chipset) nothing more happens.
