Releases: Kron4ek/Wine-Builds
Wine 10.13
10.13 release.
How to know if NTSYNC works
Note that for NTSYNC you need a new Linux kernel (6.14 or newer) and, of course, a Wine build that has NTSYNC support (like staging-tkg-ntsync).
Run something through Wine (for example, winecfg) and, while it's running, execute lsof /dev/ntsync command. If you see your Wine process IDs there, then NTSYNC works and Wine uses it, otherwise it most likely does not work. An example of working NTSYNC:
$ lsof /dev/ntsync
lsof: WARNING: can't stat() tracefs file system /sys/kernel/debug/tracing
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
start.exe 26395 user 7r CHR 10,119 0t0 1216 /dev/ntsync
wineserve 26397 user 9r CHR 10,119 0t0 1216 /dev/ntsync
services. 26401 user 14r CHR 10,119 0t0 1216 /dev/ntsync
explorer. 26407 user 8r CHR 10,119 0t0 1216 /dev/ntsync
winedevic 26441 user 8r CHR 10,119 0t0 1216 /dev/ntsync
svchost.e 26460 user 8r CHR 10,119 0t0 1216 /dev/ntsync
plugplay. 26465 user 8r CHR 10,119 0t0 1216 /dev/ntsync
winedevic 26486 user 8r CHR 10,119 0t0 1216 /dev/ntsync
conhost.e 26501 user 11r CHR 10,119 0t0 1216 /dev/ntsync
winecfg.e 26503 user 8r CHR 10,119 0t0 1216 /dev/ntsync
If you have no /dev/ntsync file at all, then your kernel either does not support NTSYNC or ntsync kernel module is not loaded, you can try to load it manually via modprobe command:
# modprobe ntsync
SHA256
65d4f5da19b7e1373293833398b807cf18431ca58025f62d9e3c2d363817d24e wine-10.13-amd64.tar.xz
4d83675231a0fcd8128e65963c1e57b6c111f4ab8167028683d33778a8249b81 wine-10.13-amd64-wow64.tar.xz
242dd0f7cc2cc564fb9cf5cb718a6934b261c8289375d441ebf1a730798ea531 wine-10.13-staging-amd64.tar.xz
630b046a055c83d0e9f5943795d5a35c74c1bbe1747c189fc53667e22dd62a0e wine-10.13-staging-amd64-wow64.tar.xz
d1f82ffa93fd526e72395a65db9c65df175c67f571e7db8b636005c1c50b9001 wine-10.13-staging-tkg-amd64.tar.xz
f1ae147d79204a76cba5ae082aa96c48a5796252aed3c4143eb855c90de5e758 wine-10.13-staging-tkg-amd64-wow64.tar.xz
5a2f56c7c82f44242b9382e813022fb79b84a7dfeffb18c053b757aa86f494c9 wine-10.13-staging-tkg-ntsync-amd64-wow64.tar.xz
48338eb22d18ec1e9d653c7243d0bf34bdee040f9513ee8b6a142fc574930644 wine-10.13-staging-tkg-x86.tar.xz
adebddde32ae8bf70a3c5b472aa35bc6a64d3530d6d3b851d59829660f86a6f4 wine-10.13-staging-x86.tar.xz
ede2a5577f724826723e5af1fd45a4f86d8c53627a879d06cc53a6f5c4a57dee wine-10.13-x86.tar.xz
Proton 10.0-2
Proton 10.0-2 release.
Note that DXVK and vkd3d-proton are not included in my wine-proton builds. If you want to use them, you need to install them into your wineprefix, the installation process is the same as with regular Wine.
SHA256
713d918fa1e01332a4924b8284366ece2ad62412776116ffe35bfb0206d5aac0 wine-proton-10.0-2-amd64.tar.xz
52ac889f299d6458a405e95e5e20b31b92839ff9811ca8b16e17b5cdb22f3e5d wine-proton-10.0-2-amd64-wow64.tar.xz
6adf5c31cae3f3aee4a726f269f2cd3078e4e4c010992758ff25f972f1b50c80 wine-proton-10.0-2-x86.tar.xz
Wine 10.12
10.12 release.
How to know if NTSYNC works
Note that for NTSYNC you need a new Linux kernel (6.14 or newer) and, of course, a Wine build that has NTSYNC support (like staging-tkg-ntsync).
Run something through Wine (for example, winecfg) and, while it's running, execute lsof /dev/ntsync command. If you see your Wine process IDs there, then NTSYNC works and Wine uses it, otherwise it most likely does not work. An example of working NTSYNC:
$ lsof /dev/ntsync
lsof: WARNING: can't stat() tracefs file system /sys/kernel/debug/tracing
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
start.exe 26395 user 7r CHR 10,119 0t0 1216 /dev/ntsync
wineserve 26397 user 9r CHR 10,119 0t0 1216 /dev/ntsync
services. 26401 user 14r CHR 10,119 0t0 1216 /dev/ntsync
explorer. 26407 user 8r CHR 10,119 0t0 1216 /dev/ntsync
winedevic 26441 user 8r CHR 10,119 0t0 1216 /dev/ntsync
svchost.e 26460 user 8r CHR 10,119 0t0 1216 /dev/ntsync
plugplay. 26465 user 8r CHR 10,119 0t0 1216 /dev/ntsync
winedevic 26486 user 8r CHR 10,119 0t0 1216 /dev/ntsync
conhost.e 26501 user 11r CHR 10,119 0t0 1216 /dev/ntsync
winecfg.e 26503 user 8r CHR 10,119 0t0 1216 /dev/ntsync
If you have no /dev/ntsync file at all, then your kernel either does not support NTSYNC or ntsync kernel module is not loaded, you can try to load it manually via modprobe command:
# modprobe ntsync
SHA256
0cf7ce173e9d89c4cbbb236f791d2dda28434583542957caa929e777415e3138 wine-10.12-amd64.tar.xz
b46c7e51aea74d8ad3836be44fd0ef2f51887a1207e4e429118fde3fed5f0096 wine-10.12-amd64-wow64.tar.xz
9926f052afb2c6a2c183a30ffed7d4e49ff4720d8aec69c65dfee04726d53151 wine-10.12-staging-amd64.tar.xz
5fa7317032846da79add307dd7364e9aee6a127ada26ed379fa8b342d6c19f95 wine-10.12-staging-amd64-wow64.tar.xz
d1c74e5e22fc78271a58ed8270f16389b172eeb1bdc34bc1c61b9ef29b9200d1 wine-10.12-staging-tkg-amd64.tar.xz
e6ec6a8213599583fa2c48e7b0c9ff5faa6a73ae01fabdfb283b5250ffe33867 wine-10.12-staging-tkg-amd64-wow64.tar.xz
4cc351f9f63321454ff0c24361b9224f88ec127438df29a749b43a47e085619c wine-10.12-staging-tkg-ntsync-amd64-wow64.tar.xz
43351c4468989f42f48dbb1b77389b1309de2da4d6327d00881643fc4e5a729f wine-10.12-staging-tkg-x86.tar.xz
fa9e4eee7f1408df072770a4a8ec42e3a1de3a97a489f838979501d5f75927d7 wine-10.12-staging-x86.tar.xz
3aa6265e3870b09f8914f10877dfff3ad8e64d1435162e253ccba6a4f8b95537 wine-10.12-x86.tar.xz
Wine 10.11
10.11 release.
How to know if NTSYNC works
Note that for NTSYNC you need a new Linux kernel (6.14 or newer) and, of course, a Wine build that has NTSYNC support (like staging-tkg-ntsync).
Run something through Wine (for example, winecfg) and, while it's running, execute lsof /dev/ntsync command. If you see your Wine process IDs there, then NTSYNC works and Wine uses it, otherwise it most likely does not work. An example of working NTSYNC:
$ lsof /dev/ntsync
lsof: WARNING: can't stat() tracefs file system /sys/kernel/debug/tracing
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
start.exe 26395 user 7r CHR 10,119 0t0 1216 /dev/ntsync
wineserve 26397 user 9r CHR 10,119 0t0 1216 /dev/ntsync
services. 26401 user 14r CHR 10,119 0t0 1216 /dev/ntsync
explorer. 26407 user 8r CHR 10,119 0t0 1216 /dev/ntsync
winedevic 26441 user 8r CHR 10,119 0t0 1216 /dev/ntsync
svchost.e 26460 user 8r CHR 10,119 0t0 1216 /dev/ntsync
plugplay. 26465 user 8r CHR 10,119 0t0 1216 /dev/ntsync
winedevic 26486 user 8r CHR 10,119 0t0 1216 /dev/ntsync
conhost.e 26501 user 11r CHR 10,119 0t0 1216 /dev/ntsync
winecfg.e 26503 user 8r CHR 10,119 0t0 1216 /dev/ntsync
If you have no /dev/ntsync file at all, then your kernel either does not support NTSYNC or ntsync kernel module is not loaded, you can try to load it manually via modprobe command:
# modprobe ntsync
SHA256
a69bd422aed47c8d6c950ad08eab48c9e5425927398e3d03e120a7d7d3f97c6c wine-10.11-amd64.tar.xz
f21f31b8160ef06bfb3adb4381a8ae61778f2b985ced8feca3e22fcd3eabe95a wine-10.11-amd64-wow64.tar.xz
eca476a1752b1504bcf648a3b20cd5b86e1e5b2f6c0d704d2d1dd1a6cec8f262 wine-10.11-staging-amd64.tar.xz
e7d93305bb87722fbfecb026811aa11cb2a09e6ae17aa54e16d25fb6949b80e3 wine-10.11-staging-amd64-wow64.tar.xz
3d22d5e3387f07314817664cc4d77e236ca51f46cf553958ac59816c1376d1c9 wine-10.11-staging-tkg-amd64.tar.xz
ca32fcc8e07c30bd196c0ffbdfba06de24161e312fa48ffa54bde4d45343e2f2 wine-10.11-staging-tkg-amd64-wow64.tar.xz
1bd50a198c4903afe7b41c4c873a8aaaeb78605fe58a409fd3c9cde6a9b8098b wine-10.11-staging-tkg-ntsync-amd64-wow64.tar.xz
c99762a9e320f2088dab228ab2ddecabb03928fafc88abef835ad3c2bf33e282 wine-10.11-staging-tkg-x86.tar.xz
11208cc36225c65f3a42397638e3f3882a9577855e252b1fd6f04ba0741c1f51 wine-10.11-staging-x86.tar.xz
e25ac6f3b484e960a640ba504a6208a3fd157b21d77785680af40783ef34cb5b wine-10.11-x86.tar.xz
Wine 10.10
10.10 release.
How to know if NTSYNC works
Note that for NTSYNC you need a new Linux kernel (6.14 or newer) and, of course, a Wine build that has NTSYNC support (like staging-tkg-ntsync).
Run something through Wine (for example, winecfg) and, while it's running, execute lsof /dev/ntsync command. If you see your Wine process IDs there, then NTSYNC works and Wine uses it, otherwise it most likely does not work. An example of working NTSYNC:
$ lsof /dev/ntsync
lsof: WARNING: can't stat() tracefs file system /sys/kernel/debug/tracing
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
start.exe 26395 user 7r CHR 10,119 0t0 1216 /dev/ntsync
wineserve 26397 user 9r CHR 10,119 0t0 1216 /dev/ntsync
services. 26401 user 14r CHR 10,119 0t0 1216 /dev/ntsync
explorer. 26407 user 8r CHR 10,119 0t0 1216 /dev/ntsync
winedevic 26441 user 8r CHR 10,119 0t0 1216 /dev/ntsync
svchost.e 26460 user 8r CHR 10,119 0t0 1216 /dev/ntsync
plugplay. 26465 user 8r CHR 10,119 0t0 1216 /dev/ntsync
winedevic 26486 user 8r CHR 10,119 0t0 1216 /dev/ntsync
conhost.e 26501 user 11r CHR 10,119 0t0 1216 /dev/ntsync
winecfg.e 26503 user 8r CHR 10,119 0t0 1216 /dev/ntsync
If you have no /dev/ntsync file at all, then your kernel either does not support NTSYNC or ntsync kernel module is not loaded, you can try to load it manually via modprobe command:
# modprobe ntsync
SHA256
9631d2a2e0673d74455006b5c5948c05f8486d3980ae5658a7a840025f498e0e wine-10.10-amd64.tar.xz
71025061f8f99def3f0c8e2cb13c68a57851f25c654461d45eabc01122e1109a wine-10.10-amd64-wow64.tar.xz
94146d35e42a9c7fccc01ea2e1bb2a6af63611f7efc55496bd93d78ab3e0476d wine-10.10-staging-amd64.tar.xz
7f67e6460b708b977990c9530dc597b372a08eb69d697dabdab5d68f7c1942c1 wine-10.10-staging-amd64-wow64.tar.xz
1d97bb21a931ac1839e9291bce9f321c80d1cc84183badbc1a86e6c42ebf678a wine-10.10-staging-tkg-amd64.tar.xz
ef40107cfeb9cc3e50decc53b84d6e3d83304866ca6c447ced5941e51a521674 wine-10.10-staging-tkg-amd64-wow64.tar.xz
100fa1659c6b707dab1905817f230eabd171d36a6098593cfa082ac909bde740 wine-10.10-staging-tkg-ntsync-amd64-wow64.tar.xz
0eb3df7a68ba9b4adc497002c368763f701ff24b065e6a52b67dafc68ae1052a wine-10.10-staging-tkg-x86.tar.xz
7e12db6e390065e95a3bed0c2b19425e98c720fee8f4f9346d1630347ed204f5 wine-10.10-staging-x86.tar.xz
2685f748bc569ffa4d23d4f1841520ad8d737523c6967537dd96b3c02cffe6cf wine-10.10-x86.tar.xz
Wine 10.9
10.9 release.
How to know if NTSYNC works
Note that for NTSYNC you need a new Linux kernel (6.14 or newer) and, of course, a Wine build that has NTSYNC support (like staging-tkg-ntsync).
Run something through Wine (for example, winecfg) and, while it's running, execute lsof /dev/ntsync command. If you see your Wine process IDs there, then NTSYNC works and Wine uses it, otherwise it most likely does not work. An example of working NTSYNC:
$ lsof /dev/ntsync
lsof: WARNING: can't stat() tracefs file system /sys/kernel/debug/tracing
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
start.exe 26395 user 7r CHR 10,119 0t0 1216 /dev/ntsync
wineserve 26397 user 9r CHR 10,119 0t0 1216 /dev/ntsync
services. 26401 user 14r CHR 10,119 0t0 1216 /dev/ntsync
explorer. 26407 user 8r CHR 10,119 0t0 1216 /dev/ntsync
winedevic 26441 user 8r CHR 10,119 0t0 1216 /dev/ntsync
svchost.e 26460 user 8r CHR 10,119 0t0 1216 /dev/ntsync
plugplay. 26465 user 8r CHR 10,119 0t0 1216 /dev/ntsync
winedevic 26486 user 8r CHR 10,119 0t0 1216 /dev/ntsync
conhost.e 26501 user 11r CHR 10,119 0t0 1216 /dev/ntsync
winecfg.e 26503 user 8r CHR 10,119 0t0 1216 /dev/ntsync
If you have no /dev/ntsync file at all, then your kernel either does not support NTSYNC or ntsync kernel module is not loaded, you can try to load it manually via modprobe command:
# modprobe ntsync
SHA256
274aa4d6eb411e86c0a55b5e80d5bf3aeef1a2fcc10d643ad162d1bb0a652307 wine-10.9-amd64.tar.xz
7e1e84f9f6f8b16afe25d4241b8d4a04988858a1fcbbd61a0a1684b772cd1c27 wine-10.9-amd64-wow64.tar.xz
9bcc87dba02a84099d2d51bda4d427ddf96763b838cff2851eb88465fe711f23 wine-10.9-staging-amd64.tar.xz
158cb6cdaafc7a482e5af81495cbcb5a47987b421da46ea49b8995efcb08b859 wine-10.9-staging-amd64-wow64.tar.xz
ba924d6010984eafe53659e25050243fd04d170e58f69ac3b416d8a27d0eee44 wine-10.9-staging-tkg-amd64.tar.xz
6fd81f4dc0ceac514a0dee6ea2b63be28889adec7dedaa79300eb7f29ade4f0e wine-10.9-staging-tkg-amd64-wow64.tar.xz
dfad05ffc3a97e2cf6f7b123f9954f0886c53b4ce139a986d2fcf70f291f73af wine-10.9-staging-tkg-ntsync-amd64-wow64.tar.xz
c4ad5fa13899bc53cf9de7f9d4123cbadb67e5a6f4a943150fb799d2cf5ef5cc wine-10.9-staging-tkg-x86.tar.xz
4ae3753d77a23e9c4aae9ec4686dedd0aeb8f1866a050dea3b667b20b7870023 wine-10.9-staging-x86.tar.xz
639751061082ae79314e69634ab6ac9ee021d202ebb8ca121a9ea1156945c4c6 wine-10.9-x86.tar.xz
Wine 10.8
10.8 release.
How to know if NTSYNC works
Note that for NTSYNC you need a new Linux kernel (6.14 or newer) and, of course, a Wine build that has NTSYNC support (like staging-tkg-ntsync).
Run something through Wine (for example, winecfg) and, while it's running, execute lsof /dev/ntsync command. If you see your Wine process IDs there, then NTSYNC works and Wine uses it, otherwise it most likely does not work. An example of working NTSYNC:
$ lsof /dev/ntsync
lsof: WARNING: can't stat() tracefs file system /sys/kernel/debug/tracing
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
start.exe 26395 user 7r CHR 10,119 0t0 1216 /dev/ntsync
wineserve 26397 user 9r CHR 10,119 0t0 1216 /dev/ntsync
services. 26401 user 14r CHR 10,119 0t0 1216 /dev/ntsync
explorer. 26407 user 8r CHR 10,119 0t0 1216 /dev/ntsync
winedevic 26441 user 8r CHR 10,119 0t0 1216 /dev/ntsync
svchost.e 26460 user 8r CHR 10,119 0t0 1216 /dev/ntsync
plugplay. 26465 user 8r CHR 10,119 0t0 1216 /dev/ntsync
winedevic 26486 user 8r CHR 10,119 0t0 1216 /dev/ntsync
conhost.e 26501 user 11r CHR 10,119 0t0 1216 /dev/ntsync
winecfg.e 26503 user 8r CHR 10,119 0t0 1216 /dev/ntsync
If you have no /dev/ntsync file at all, then your kernel either does not support NTSYNC or ntsync kernel module is not loaded, you can try to load it manually via modprobe command:
# modprobe ntsync
SHA256
2872463874055719bdb9209e6ac459a91b1a045ab011e6d13149f7e80e3ef92b wine-10.8-amd64.tar.xz
4fa563b32de862e8e058836b45ec56a0efa8d1bb75366b2d1d0505b05136aa27 wine-10.8-amd64-wow64.tar.xz
7138f38a474e36c6db44a3aebb32b1f5e811dd3e38b4a016ee3999a0ac798917 wine-10.8-staging-amd64.tar.xz
cdd6effc2a61c66b5dbfb8aebbc08df151cd50bf9084b106bfef0d6ebc7b097f wine-10.8-staging-amd64-wow64.tar.xz
8f85eb1d64c0dd1dd16c4ab56db08fbeb8adc9d5a058ff3acef1cbb8194b010d wine-10.8-staging-tkg-amd64.tar.xz
573eabd3555ecc5c974b1fbe35b3ef32d4a77faeb2ea4b77e1de9c290b3941af wine-10.8-staging-tkg-amd64-wow64.tar.xz
536a853de65372f68d8563aa2cf9e25e9e3ac2366e8a770cc40437fc0be76047 wine-10.8-staging-tkg-ntsync-amd64-wow64.tar.xz
4c300688b24897eacbb30072a71f056bbbff9b28c987767b315dcfbd2c69a789 wine-10.8-staging-tkg-x86.tar.xz
c2a3cbb45df7f7249f3df05475e06a3b43deacbfe0c7fe39b54a4cf501c96a45 wine-10.8-staging-x86.tar.xz
5c07601ff66f48e3300dffd3a6ba37479a8cfa5b8f47f196f8a02b1fd0d38191 wine-10.8-x86.tar.xz
Wine 10.7
10.7 release.
How to know if NTSYNC works
Note that for NTSYNC you need a new Linux kernel (6.14 or newer) and, of course, a Wine build that has NTSYNC support (like staging-tkg-ntsync).
Run something through Wine (for example, winecfg) and, while it's running, execute lsof /dev/ntsync command. If you see your Wine process IDs there, then NTSYNC works and Wine uses it, otherwise it most likely does not work. An example of working NTSYNC:
$ lsof /dev/ntsync
lsof: WARNING: can't stat() tracefs file system /sys/kernel/debug/tracing
Output information may be incomplete.
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
start.exe 26395 user 7r CHR 10,119 0t0 1216 /dev/ntsync
wineserve 26397 user 9r CHR 10,119 0t0 1216 /dev/ntsync
services. 26401 user 14r CHR 10,119 0t0 1216 /dev/ntsync
explorer. 26407 user 8r CHR 10,119 0t0 1216 /dev/ntsync
winedevic 26441 user 8r CHR 10,119 0t0 1216 /dev/ntsync
svchost.e 26460 user 8r CHR 10,119 0t0 1216 /dev/ntsync
plugplay. 26465 user 8r CHR 10,119 0t0 1216 /dev/ntsync
winedevic 26486 user 8r CHR 10,119 0t0 1216 /dev/ntsync
conhost.e 26501 user 11r CHR 10,119 0t0 1216 /dev/ntsync
winecfg.e 26503 user 8r CHR 10,119 0t0 1216 /dev/ntsync
If you have no /dev/ntsync file at all, then your kernel either does not support NTSYNC or ntsync kernel module is not loaded, you can try to load it manually via modprobe command:
# modprobe ntsync
SHA256
b35574ec659d861c544ec185ff015967fad4def228c8a9744077b23f5b9aa389 wine-10.7-amd64.tar.xz
fe9f9099c4b5a0d6f0de1ed5c8718c5906dd03cd3b91f3f56e36416454c1a629 wine-10.7-amd64-wow64.tar.xz
b35864aca52c88982ed2c426392e1e51bd4f0dc3f5879dbdeac1e026c53b5b53 wine-10.7-staging-amd64.tar.xz
540c651915f1d6a5244886c153dd092f09368b12289cfb7bcee5886d1bca69fd wine-10.7-staging-amd64-wow64.tar.xz
45635677b0794aedab19eba03088b1432ed8b9b202fd9910b347cdaf742755ff wine-10.7-staging-tkg-amd64.tar.xz
8d1583676fd236c93022c1993acf0132e632bbdbcd9dcc4a68a3a629072a41b7 wine-10.7-staging-tkg-amd64-wow64.tar.xz
131e38890905025413ed50948285e0f6fd7e4671f9a9d5e68bba82a2b0fe8dd2 wine-10.7-staging-tkg-ntsync-amd64-wow64.tar.xz
e9d5ae6938e7498757e57508662c636d3aee49450822dbf734933f836fb03e02 wine-10.7-staging-tkg-x86.tar.xz
0a29761308c498a98d57729a4b4e605939fa0a51975763e9f51f909a010bfd54 wine-10.7-staging-x86.tar.xz
5a13e50703c0746bac3d3ccb5cf2da02578f33b2178ae67c3d7c0b3e54b2acc4 wine-10.7-x86.tar.xz
Proton Experimental 10.0
Proton Experimental 10.0 (compiled from ValveSoftware/wine@d0d4618).
Note that DXVK and vkd3d-proton are not included in my wine-proton builds. If you want to use them, you need to install them into your wineprefix, the installation process is the same as with regular Wine.
SHA256
1b3344a8ec731b4446e982d66469aca81166fd30f2079868855d8464d289fc57 wine-proton-exp-10.0-amd64.tar.xz
cc2e78084365eca3ac6177a89b2cdf1c1176bf01c2c6dd7e912156db4426b41f wine-proton-exp-10.0-amd64-wow64.tar.xz
7bd75208e98fe601b493a2ef7603efe2510885a613490ca7b70f4baaee1c42f0 wine-proton-exp-10.0-x86.tar.xz
Updated 12.07.25 12:53 (DMY UTC).
Proton 10.0-1
Proton 10.0-1 release.
Note that DXVK and vkd3d-proton are not included in my wine-proton builds. If you want to use them, you need to install them into your wineprefix, the installation process is the same as with regular Wine.
SHA256
ead2ad14643fc711a23501643a181589b347d1335c2aa43c137823654290c640 wine-proton-10.0-1-amd64.tar.xz
d8c3648e062adb7e6d604691863b2d8f2359e9c105ea0d69f721c5f123edc94e wine-proton-10.0-1-x86.tar.xz