Leaderboard

# [Windows 8.1 x64] Cyberpunk 2077 2.31 Steam compatibility patch I am publishing an experimental compatibility package for **Cyberpunk 2077 2.31 on Windows 8.1 x64**, tested against the Steam public build `20383525`. ** Download has been taken down **ZIP SHA-256:** `5D8543335269D86B7456B60B6E6A3908C6C296B186DB93F8EF25EA38D371745E` > This release was tested only on **Windows 8.1 x64**, so that is the only > operating system for which it is currently recommended. The installer rejects > other Windows versions and unsupported game files. ## What it fixes The package provides a D3D12On7 raster path for the tested Steam build and fixes the known presentation problem where Cyberpunk appears frozen and updates only when another window is dragged over it. The game can be launched normally with Steam's **Play** button after adding the launch option printed by the installer. ## Performance On my tested machine, performance is close to running the game on Windows 10. It is dramatically better than my older Cyberpunk 1.63 compatibility setup, which delivered roughly half performance on the same machine. This is an observed real-world comparison, **not a controlled or standardized benchmark**. Results will vary with GPU, driver, settings and system setup. ## Tested setup - Windows 8.1 x64 - Cyberpunk 2077 2.31, Steam build `20383525` - GeForce RTX 2060 - NVIDIA driver `474.11` - 1920 x 1080 - Raster rendering only Other GPUs and drivers, GOG/Epic releases, hybrid graphics and other operating systems have not been tested. ## Required: official D3D12On7 1.1.0 package Download Microsoft's official [`Microsoft.Direct3D.D3D12On7` 1.1.0 NuGet package](https://www.nuget.org/packages/Microsoft.Direct3D.D3D12On7/1.1.0) separately and save the unchanged file next to `Install.cmd` as: `Microsoft.Direct3D.D3D12On7.1.1.0.nupkg` Expected package SHA-256: `C0C4D597537ECC1C777FA3B5523E5CCDE0B9984B88FB9F37B2385E1D687BF536` The Microsoft package is not bundled with this patch. ## Required: SecondSystem SecondSystem must already be installed and active. **It is not bundled with the patch.** Obtain it separately here: [SecondSystem from win32's Patreon](https://patreon.com/win32?utm_medium=clipboard_copy&utm_source=copyLink&utm_campaign=creatorshare_fan&utm_content=join_link) Please support its developer and follow the terms provided with it. ## Installation 1. Extract the complete ZIP. 2. Download the official D3D12On7 package above and place it beside `Install.cmd`. 3. Install and activate SecondSystem. 4. Exit both Cyberpunk 2077 and Steam completely. 5. Run `Install.cmd`. 6. Copy the exact Steam Launch Options value printed at the end. 7. Paste it into **Steam > Cyberpunk 2077 > Properties > General > Launch Options**. 8. Start the game with Steam's **Play** button. Do not append custom arguments; the included launcher intentionally uses only the fixed, validated command line. The installer validates the exact game/runtime hashes and stops before changing anything if the files are unsupported. It keeps all compatibility files local to the game directory and creates a verified uninstall record. ## Important limitations The following features must remain disabled: - Ray tracing and path tracing - DLSS - NVIDIA Reflex - Frame Generation, including XeSS Frame Generation This release is for raster rendering. Cyberpunk 2.31's newer Agility SDK path is not a Windows 8.1 target, so modern features that depend on it are outside this patch's scope. ## Removal and game updates Close the game and Steam, run `Uninstall.cmd`, then clear Steam Launch Options. The uninstaller restores any files it backed up and reverses its SecondSystem mappings. The package is locked to Steam build `20383525`. The launcher compares the full contents of the current executable with its validated local copy and refuses a mismatch. After a Steam update, uninstall this release and wait for a version explicitly validated for the new build; do not remove the version/hash safety checks. ## What is and is not included The ZIP contains the original open-source proxy, launcher, installer scripts, source code, documentation and notices. It does **not** include: - Cyberpunk 2077 files - Microsoft D3D12On7 or D3D11On12 binaries - SecondSystem - Steam files - any DRM bypass A legal Steam copy of the game is required. The installer extracts the runtime inputs from the official NuGet package separately supplied by the user and creates a local working copy. Microsoft terms still apply and may restrict this use or modification; this is not legal advice. Full installation, troubleshooting, technical and checksum information is in the included `README.md`.

I've had the same issues with the Dutch language pack. Some things have to be changed in the .xpi file. Regarding the German language pack; @AstroSkipper should be able to help you out.

good point, i often said going to start with v150 or something is a little to much

I managed to fix my issue. Here's how: I installed windows NT 4.0 to virtualbox 6.0 on windows 8.1 as per this guide https://i12bretro.github.io/tutorials/0077.html. I made the VM's hard disk as a VHD file *IMPORTANT*. However, instead of installing to NTFS, I installed to FAT. (This did not require me to preformat the partition, but I expected it to). I also gave the VM 4 GB of RAM and a 1024MB hard drive. Then, after booting the VM and it working, I used the action menu in windows disk manager (create and format hard disk partitions) to mount the VHD file of the VM. Then, I used minitool partition wizard 9.0 free to copy the partition to the correct spot on my drives (and resize it to 2GB). Then, I used EasyBCD to make the new boot menu entry for it, as well as deleting the previous entry for NT 4.0, since the partition was overridden by the new install. I had to make sure that the disk that NT 4.0 is on is plugged into one of the first 3 sata ports as those are the first emulated sata/IDE controller and NT 4.0 cannot access the second one during the boot sequence. Since my NT 4.0 is within the first 131GB of the drive, I did not have to install LBA48 supporting disk drivers, but drivers such as UniATA exist. Once booted in, I installed the USB patch for windows NT 4.0 (after changing the drive letter of NT 4.0's partition to C: *important*) and force rebooted the computer to get the mouse to work (must wait approx 1 min after the computer has started for it to pick up the mouse and keyboard). Then, I removed drive letters from all partitions besides Win NT itself and the other "unknown" partition on another disk that it won't let me de-letter ("boot drives MUST have a letter"). Once in this state, my issue was fixed. Windows 7 no longer becomes a sluggish nightmare after booting into windows NT 4.0, but windows 7 can still access all drives and partitions, including NT 4.0's. I believe that I could even get NT 4.0 to see all the partitions that it could with UniATA and still not have issues, but I don't really care and would rather not find out. I did not delete NTFS.SYS or disable the service/device as I did not need to. I now have installed USB and video drivers. Besides sound, I call NT 4.0 complete. Thanks for all the help, even if the long way ended up being the answer. All that's left for my system to be complete is to install Windows 10 (throughout one process or another (I believe trying to fix windows 2000 before) it got corrupted and deleted), and make sure everything is 100% ready to go. I would love to get audio on 95, 3.1, and NT 4.0, but that would be for another thread. Again, thanks!

I just got a FAT16 installed NT 4.0 onto my system! I have to re-figure out USB, drive letters, graphics, and more, as well as stop NTFS.SYS from starting. I'll get back soon!

Sorry for the delay in responding again. Nothing has changed since my last report, the program is working, with my folder exclusions applied, with only occasional stops and restarts of the main Panda service. I can live with that in the short term. I'm still hoping, of course, that a fix will be applied and it will all come good again. Nobody has any definite evidence that Panda have deliberately stopped their XP version from working properly, only speculation. I will wait a while and ring AnyTech365 again if I've heard nothing from them about this. They will be as anxious as I am to get an answer from the Panda developers about this, I'm sure, as they will need to be able to give accurate support information to anyone else asking about this problem! Assuming that they do have a direct channel of communication to them, and it would be pretty stupid if they didn't, hopefully it won't be too long a wait for an answer, one way or the other.

Since CIS 12.0.0.6870 is also the last compatible version with Vista SP2 x86, I, too, have a vested interest in obtaining the off-line installer for that version ; a quick search led me to https://forums.comodo.com/t/how-download-full-installation-of-older-versions-cis-official-links-wrong/320847 but, sadly, the Internet Archive hasn't salvaged it (they only have v12.0.0.6882, the one after it, which is Win7+ ); other archiving services don't seem to have it, either ... Will you be willing to share a download link? And will you be disclosing any info about the needed "medications" to "resuscitate" it ? Thanks for your time and efforts ...

Et tu, Brute?