3DMark uses a low-level system information gatherer. On first launch (or after a Windows update), it must compile a kernel driver on-the-fly. Antivirus software (McAfee, Norton, even Windows Defender) often quarantines this compilation step because it looks like a rootkit installer.
Sometimes, the problem is on UL Solutions' end. The 3DMark servers occasionally go down for maintenance or get slammed during Steam sales. 3dmark stuck on starting ui
Steam auto-updates 3DMark to the latest version (which often introduces new UI bugs). UL offers a standalone Professional Edition installer on their website. Download the offline installer from your UL account (if you own a key) or use the "3DMark Demo" standalone from their FTP archive. The 2.25.x versions are notably more stable than the 2.28.x branch. 3DMark uses a low-level system information gatherer
The "stuck on starting UI" or "initializing" error is typically caused by a hang in the Futuremark SystemInfo service as it attempts to scan your hardware components. This scan can stall due to conflicting background software, corrupted installation files, or outdated system frameworks. Quick Fixes for Common Startup Hangs Sometimes, the problem is on UL Solutions' end
: Open Task Manager ( Ctrl + Shift + Esc ) and look for processes named adapter_info.exe or dxr_info.exe . Ending these tasks often bypasses the hang and allows the UI to load immediately.