API tools faq
paste
superken54

ds4windows log

superken54
Oct 5th, 2026
15
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 35.72 KB | None | 0 0
raw download clone embed print report
  1. 2026-09-19T16:50:01.3937162-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 started ===
  2. 2026-09-19T16:50:01.4151226-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 completed with exit code 0 ===
  3. 2026-09-19T16:50:08.3138494-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 started ===
  4. 2026-09-19T16:50:08.3424991-05:00 Removed obsolete bundled VIIPER payload: C:\Program Files\DS4Windows\extras\VIIPER-0.1.0-x64.exe
  5. 2026-09-19T16:50:08.3434011-05:00 Removed obsolete bundled VIIPER payload: C:\Program Files\DS4Windows\extras\VIIPER-0.1.0-x64.exe.sha256
  6. 2026-09-19T16:50:08.3492858-05:00 Infrastructure setup starting for interactive user AJ\antio (S-1-5-21-2418015503-3615739347-2779590200-1001).
  7. 2026-09-19T16:50:19.5493563-05:00 The all-in-one installer owns the cross-session setup mutex through child verification and reboot-resume staging.
  8.  
  9. DS4Windows VIIPER virtual controller setup
  10. Standard: install DS4Windows and VIIPER in Program Files.
  11. Planned order:
  12. 1. Install VIIPER and register both elevated startup tasks.
  13. 2. Verify or install packaged usbip-win2 0.9.7.7.
  14. 3. Verify the startup tasks remain exact and enabled.
  15. 4. Start and verify the local VIIPER API.
  16. USB hub devices may restart during driver replacement, and Windows may require a reboot.
  17. Protected DS4Windows package files from unelevated replacement: C:\Program Files\DS4Windows
  18. Protected VIIPER package files from unelevated replacement: C:\Program Files\DS4Windows\VIIPER
  19.  
  20. Setup authorized; beginning verified installation.
  21.  
  22. == Step 1 of 4 - Installing VIIPER 0.1.0 ==
  23.  
  24. Failure containment verified 'RunVIIPER' is disabled.
  25. Setup could not finish: The offline DS4Windows package is incomplete: missing VIIPER-0.1.0-x64.exe.
  26. Details were saved to C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  27.  
  28.  
  29. 2026-09-19T16:50:19.5525046-05:00 Infrastructure setup exited with code 1. Detailed log: C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  30. 2026-09-19T16:50:19.5533102-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 completed with exit code 1 ===
  31. 2026-09-19T16:51:09.8833838-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 started ===
  32. 2026-09-19T16:51:09.9042422-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 completed with exit code 0 ===
  33. 2026-09-19T16:51:14.5750928-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 started ===
  34. 2026-09-19T16:51:14.5964355-05:00 Infrastructure setup starting for interactive user AJ\antio (S-1-5-21-2418015503-3615739347-2779590200-1001).
  35. 2026-09-19T16:51:24.8132041-05:00 The all-in-one installer owns the cross-session setup mutex through child verification and reboot-resume staging.
  36.  
  37. DS4Windows VIIPER virtual controller setup
  38. Standard: install DS4Windows and VIIPER in Program Files.
  39. Planned order:
  40. 1. Install VIIPER and register both elevated startup tasks.
  41. 2. Verify or install packaged usbip-win2 0.9.7.7.
  42. 3. Verify the startup tasks remain exact and enabled.
  43. 4. Start and verify the local VIIPER API.
  44. USB hub devices may restart during driver replacement, and Windows may require a reboot.
  45. Protected DS4Windows package files from unelevated replacement: C:\Program Files\DS4Windows
  46. Protected VIIPER package files from unelevated replacement: C:\Program Files\DS4Windows\VIIPER
  47.  
  48. Setup authorized; beginning verified installation.
  49.  
  50. == Step 1 of 4 - Installing VIIPER 0.1.5-rc4.6 ==
  51. Using packaged VIIPER 0.1.5-rc4.6 x64 binary.
  52. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  53. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  54. Preserved previous startup task 'RunVIIPER': C:\ProgramData\DS4Windows\Installer\task-backups\RunVIIPER-857623619E36951DBFA898DCF3B918744ED0D3015634A6FF7DC3CB1E81D7B449.xml
  55. Disabled existing VIIPER startup until setup verifies the driver ABI.
  56. VIIPER installed to C:\Program Files\DS4Windows\VIIPER\viiper.exe
  57. Windows Installer managed DS4Windows copy and startup target: C:\Program Files\DS4Windows\DS4Windows.exe
  58. Protected elevated VIIPER startup executable: C:\Program Files\DS4Windows\VIIPER\viiper.exe
  59. Protected elevated DS4Windows startup executable: C:\Program Files\DS4Windows\DS4Windows.exe
  60. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  61.  
  62. == Step 2 of 4 - Checking usbip-win2 0.9.7.7 ==
  63.  
  64. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  65. Setup could not finish: USBIP driver or package artifacts exist, but canonical usbip.exe is missing. Refusing to change a driver whose active imports cannot be inspected safely. Repair or remove USBIP manually, reboot, then run setup again.
  66. Details were saved to C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  67.  
  68.  
  69. 2026-09-19T16:51:24.8167761-05:00 Infrastructure setup exited with code 1. Detailed log: C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  70. 2026-09-19T16:51:24.8177208-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 completed with exit code 1 ===
  71. 2026-09-19T16:52:09.7439496-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 started ===
  72. 2026-09-19T16:52:09.7646926-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 completed with exit code 0 ===
  73. 2026-09-19T16:52:14.4122851-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 started ===
  74. 2026-09-19T16:52:14.4335771-05:00 Infrastructure setup starting for interactive user AJ\antio (S-1-5-21-2418015503-3615739347-2779590200-1001).
  75. 2026-09-19T16:52:22.5714793-05:00 The all-in-one installer owns the cross-session setup mutex through child verification and reboot-resume staging.
  76.  
  77. DS4Windows VIIPER virtual controller setup
  78. Standard: install DS4Windows and VIIPER in Program Files.
  79. Planned order:
  80. 1. Install VIIPER and register both elevated startup tasks.
  81. 2. Verify or install packaged usbip-win2 0.9.7.7.
  82. 3. Verify the startup tasks remain exact and enabled.
  83. 4. Start and verify the local VIIPER API.
  84. USB hub devices may restart during driver replacement, and Windows may require a reboot.
  85. Protected DS4Windows package files from unelevated replacement: C:\Program Files\DS4Windows
  86. Protected VIIPER package files from unelevated replacement: C:\Program Files\DS4Windows\VIIPER
  87.  
  88. Setup authorized; beginning verified installation.
  89.  
  90. == Step 1 of 4 - Installing VIIPER 0.1.5-rc4.6 ==
  91. Using packaged VIIPER 0.1.5-rc4.6 x64 binary.
  92. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  93. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  94. Disabled existing VIIPER startup until setup verifies the driver ABI.
  95. VIIPER installed to C:\Program Files\DS4Windows\VIIPER\viiper.exe
  96. Windows Installer managed DS4Windows copy and startup target: C:\Program Files\DS4Windows\DS4Windows.exe
  97. Protected elevated VIIPER startup executable: C:\Program Files\DS4Windows\VIIPER\viiper.exe
  98. Protected elevated DS4Windows startup executable: C:\Program Files\DS4Windows\DS4Windows.exe
  99. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  100.  
  101. == Step 2 of 4 - Checking usbip-win2 0.9.7.7 ==
  102.  
  103. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  104. Setup could not finish: USBIP driver or package artifacts exist, but canonical usbip.exe is missing. Refusing to change a driver whose active imports cannot be inspected safely. Repair or remove USBIP manually, reboot, then run setup again.
  105. Details were saved to C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  106.  
  107.  
  108. 2026-09-19T16:52:22.5746633-05:00 Infrastructure setup exited with code 1. Detailed log: C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  109. 2026-09-19T16:52:22.5756786-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 completed with exit code 1 ===
  110. 2026-09-19T16:54:12.7158317-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 started ===
  111. 2026-09-19T16:54:12.7359962-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 completed with exit code 0 ===
  112. 2026-09-19T16:54:17.5399721-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 started ===
  113. 2026-09-19T16:54:17.5619356-05:00 Infrastructure setup starting for interactive user AJ\antio (S-1-5-21-2418015503-3615739347-2779590200-1001).
  114. 2026-09-19T16:54:25.2223622-05:00 The all-in-one installer owns the cross-session setup mutex through child verification and reboot-resume staging.
  115.  
  116. DS4Windows VIIPER virtual controller setup
  117. Standard: install DS4Windows and VIIPER in Program Files.
  118. Planned order:
  119. 1. Install VIIPER and register both elevated startup tasks.
  120. 2. Verify or install packaged usbip-win2 0.9.7.7.
  121. 3. Verify the startup tasks remain exact and enabled.
  122. 4. Start and verify the local VIIPER API.
  123. USB hub devices may restart during driver replacement, and Windows may require a reboot.
  124. Protected DS4Windows package files from unelevated replacement: C:\Program Files\DS4Windows
  125. Protected VIIPER package files from unelevated replacement: C:\Program Files\DS4Windows\VIIPER
  126.  
  127. Setup authorized; beginning verified installation.
  128.  
  129. == Step 1 of 4 - Installing VIIPER 0.1.5-rc4.6 ==
  130. Using packaged VIIPER 0.1.5-rc4.6 x64 binary.
  131. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  132. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  133. Disabled existing VIIPER startup until setup verifies the driver ABI.
  134. VIIPER installed to C:\Program Files\DS4Windows\VIIPER\viiper.exe
  135. Windows Installer managed DS4Windows copy and startup target: C:\Program Files\DS4Windows\DS4Windows.exe
  136. Protected elevated VIIPER startup executable: C:\Program Files\DS4Windows\VIIPER\viiper.exe
  137. Protected elevated DS4Windows startup executable: C:\Program Files\DS4Windows\DS4Windows.exe
  138. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  139.  
  140. == Step 2 of 4 - Checking usbip-win2 0.9.7.7 ==
  141.  
  142. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  143. Setup could not finish: USBIP driver or package artifacts exist, but canonical usbip.exe is missing. Refusing to change a driver whose active imports cannot be inspected safely. Repair or remove USBIP manually, reboot, then run setup again.
  144. Details were saved to C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  145.  
  146.  
  147. 2026-09-19T16:54:25.2246789-05:00 Infrastructure setup exited with code 1. Detailed log: C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  148. 2026-09-19T16:54:25.2253885-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 completed with exit code 1 ===
  149. 2026-09-19T16:55:06.2041440-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 started ===
  150. 2026-09-19T16:55:06.2255504-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 completed with exit code 0 ===
  151. 2026-09-19T16:55:11.5710831-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 started ===
  152. 2026-09-19T16:55:11.5924796-05:00 Infrastructure setup starting for interactive user AJ\antio (S-1-5-21-2418015503-3615739347-2779590200-1001).
  153. 2026-09-19T16:55:18.8194202-05:00 The all-in-one installer owns the cross-session setup mutex through child verification and reboot-resume staging.
  154.  
  155. DS4Windows VIIPER virtual controller setup
  156. Standard: install DS4Windows and VIIPER in Program Files.
  157. Planned order:
  158. 1. Install VIIPER and register both elevated startup tasks.
  159. 2. Verify or install packaged usbip-win2 0.9.7.7.
  160. 3. Verify the startup tasks remain exact and enabled.
  161. 4. Start and verify the local VIIPER API.
  162. USB hub devices may restart during driver replacement, and Windows may require a reboot.
  163. Protected DS4Windows package files from unelevated replacement: C:\Program Files\DS4Windows
  164. Protected VIIPER package files from unelevated replacement: C:\Program Files\DS4Windows\VIIPER
  165.  
  166. Setup authorized; beginning verified installation.
  167.  
  168. == Step 1 of 4 - Installing VIIPER 0.1.5-rc4.6 ==
  169. Using packaged VIIPER 0.1.5-rc4.6 x64 binary.
  170. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  171. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  172. Disabled existing VIIPER startup until setup verifies the driver ABI.
  173. VIIPER installed to C:\Program Files\DS4Windows\VIIPER\viiper.exe
  174. Windows Installer managed DS4Windows copy and startup target: C:\Program Files\DS4Windows\DS4Windows.exe
  175. Protected elevated VIIPER startup executable: C:\Program Files\DS4Windows\VIIPER\viiper.exe
  176. Protected elevated DS4Windows startup executable: C:\Program Files\DS4Windows\DS4Windows.exe
  177. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  178.  
  179. == Step 2 of 4 - Checking usbip-win2 0.9.7.7 ==
  180.  
  181. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  182. Setup could not finish: USBIP driver or package artifacts exist, but canonical usbip.exe is missing. Refusing to change a driver whose active imports cannot be inspected safely. Repair or remove USBIP manually, reboot, then run setup again.
  183. Details were saved to C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  184.  
  185.  
  186. 2026-09-19T16:55:18.8219068-05:00 Infrastructure setup exited with code 1. Detailed log: C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  187. 2026-09-19T16:55:18.8226571-05:00 === DS4Windows setup invocation fbfdf4b8f523424ba33cec9f15d30136 completed with exit code 1 ===
  188. 2026-09-19T16:55:49.3003908-05:00 === DS4Windows setup invocation 7f60b299e0644269b7cd76639ad41987 started ===
  189. 2026-09-19T16:55:49.3211551-05:00 === DS4Windows setup invocation 7f60b299e0644269b7cd76639ad41987 completed with exit code 0 ===
  190. 2026-09-19T16:55:54.4990820-05:00 === DS4Windows setup invocation 7f60b299e0644269b7cd76639ad41987 started ===
  191. 2026-09-19T16:55:54.5213886-05:00 Infrastructure setup starting for interactive user AJ\antio (S-1-5-21-2418015503-3615739347-2779590200-1001).
  192. 2026-09-19T16:56:02.2777138-05:00 The all-in-one installer owns the cross-session setup mutex through child verification and reboot-resume staging.
  193.  
  194. DS4Windows VIIPER virtual controller setup
  195. Standard: install DS4Windows and VIIPER in Program Files.
  196. Planned order:
  197. 1. Install VIIPER and register both elevated startup tasks.
  198. 2. Verify or install packaged usbip-win2 0.9.7.7.
  199. 3. Verify the startup tasks remain exact and enabled.
  200. 4. Start and verify the local VIIPER API.
  201. USB hub devices may restart during driver replacement, and Windows may require a reboot.
  202. Protected DS4Windows package files from unelevated replacement: C:\Program Files\DS4Windows
  203. Protected VIIPER package files from unelevated replacement: C:\Program Files\DS4Windows\VIIPER
  204.  
  205. Setup authorized; beginning verified installation.
  206.  
  207. == Step 1 of 4 - Installing VIIPER 0.1.5-rc4.6 ==
  208. Using packaged VIIPER 0.1.5-rc4.6 x64 binary.
  209. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  210. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  211. Disabled existing VIIPER startup until setup verifies the driver ABI.
  212. VIIPER installed to C:\Program Files\DS4Windows\VIIPER\viiper.exe
  213. Windows Installer managed DS4Windows copy and startup target: C:\Program Files\DS4Windows\DS4Windows.exe
  214. Protected elevated VIIPER startup executable: C:\Program Files\DS4Windows\VIIPER\viiper.exe
  215. Protected elevated DS4Windows startup executable: C:\Program Files\DS4Windows\DS4Windows.exe
  216. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  217.  
  218. == Step 2 of 4 - Checking usbip-win2 0.9.7.7 ==
  219.  
  220. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  221. Setup could not finish: USBIP driver or package artifacts exist, but canonical usbip.exe is missing. Refusing to change a driver whose active imports cannot be inspected safely. Repair or remove USBIP manually, reboot, then run setup again.
  222. Details were saved to C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  223.  
  224.  
  225. 2026-09-19T16:56:02.2805725-05:00 Infrastructure setup exited with code 1. Detailed log: C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  226. 2026-09-19T16:56:02.2818365-05:00 === DS4Windows setup invocation 7f60b299e0644269b7cd76639ad41987 completed with exit code 1 ===
  227. 2026-09-19T17:02:51.2141327-05:00 === DS4Windows setup invocation 128029928ead4f2283fb620965a8da2b started ===
  228. 2026-09-19T17:02:51.2558225-05:00 === DS4Windows setup invocation 128029928ead4f2283fb620965a8da2b completed with exit code 0 ===
  229. 2026-09-19T17:02:55.8032566-05:00 === DS4Windows setup invocation 128029928ead4f2283fb620965a8da2b started ===
  230. 2026-09-19T17:02:55.8244755-05:00 Infrastructure setup starting for interactive user AJ\antio (S-1-5-21-2418015503-3615739347-2779590200-1001).
  231. 2026-09-19T17:03:09.0070267-05:00 The all-in-one installer owns the cross-session setup mutex through child verification and reboot-resume staging.
  232.  
  233. DS4Windows VIIPER virtual controller setup
  234. Standard: install DS4Windows and VIIPER in Program Files.
  235. Planned order:
  236. 1. Install VIIPER and register both elevated startup tasks.
  237. 2. Verify or install packaged usbip-win2 0.9.7.7.
  238. 3. Verify the startup tasks remain exact and enabled.
  239. 4. Start and verify the local VIIPER API.
  240. USB hub devices may restart during driver replacement, and Windows may require a reboot.
  241. Protected DS4Windows package files from unelevated replacement: C:\Program Files\DS4Windows
  242. Protected VIIPER package files from unelevated replacement: C:\Program Files\DS4Windows\VIIPER
  243.  
  244. Setup authorized; beginning verified installation.
  245.  
  246. == Step 1 of 4 - Installing VIIPER 0.1.5-rc4.6 ==
  247. Using packaged VIIPER 0.1.5-rc4.6 x64 binary.
  248. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  249. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  250. Disabled existing VIIPER startup until setup verifies the driver ABI.
  251. VIIPER installed to C:\Program Files\DS4Windows\VIIPER\viiper.exe
  252. Windows Installer managed DS4Windows copy and startup target: C:\Program Files\DS4Windows\DS4Windows.exe
  253. Protected elevated VIIPER startup executable: C:\Program Files\DS4Windows\VIIPER\viiper.exe
  254. Protected elevated DS4Windows startup executable: C:\Program Files\DS4Windows\DS4Windows.exe
  255. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  256.  
  257. == Step 2 of 4 - Checking usbip-win2 0.9.7.7 ==
  258. usbip-win2 is unsupported (0.9.8.0); installing or repairing 0.9.7.7.
  259.  
  260. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  261. Setup could not finish: The exact usbip-win2 AppId record has unexpected package identity metadata. No driver transition was started.
  262. Details were saved to C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  263.  
  264.  
  265. 2026-09-19T17:03:09.0092567-05:00 Infrastructure setup exited with code 1. Detailed log: C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  266. 2026-09-19T17:03:09.0097221-05:00 === DS4Windows setup invocation 128029928ead4f2283fb620965a8da2b completed with exit code 1 ===
  267. 2026-09-19T17:13:56.0988079-05:00 === DS4Windows setup invocation 45d9d2fb9c3342a3904c24cbbb6d2e55 started ===
  268. 2026-09-19T17:13:56.1193459-05:00 === DS4Windows setup invocation 45d9d2fb9c3342a3904c24cbbb6d2e55 completed with exit code 0 ===
  269. 2026-09-19T17:14:01.3922891-05:00 === DS4Windows setup invocation 45d9d2fb9c3342a3904c24cbbb6d2e55 started ===
  270. 2026-09-19T17:14:01.4133666-05:00 Infrastructure setup starting for interactive user AJ\antio (S-1-5-21-2418015503-3615739347-2779590200-1001).
  271. 2026-09-19T17:14:16.2932155-05:00 The all-in-one installer owns the cross-session setup mutex through child verification and reboot-resume staging.
  272.  
  273. DS4Windows VIIPER virtual controller setup
  274. Standard: install DS4Windows and VIIPER in Program Files.
  275. Planned order:
  276. 1. Install VIIPER and register both elevated startup tasks.
  277. 2. Verify or install packaged usbip-win2 0.9.7.7.
  278. 3. Verify the startup tasks remain exact and enabled.
  279. 4. Start and verify the local VIIPER API.
  280. USB hub devices may restart during driver replacement, and Windows may require a reboot.
  281. Protected DS4Windows package files from unelevated replacement: C:\Program Files\DS4Windows
  282. Protected VIIPER package files from unelevated replacement: C:\Program Files\DS4Windows\VIIPER
  283.  
  284. Setup authorized; beginning verified installation.
  285.  
  286. == Step 1 of 4 - Installing VIIPER 0.1.5-rc4.6 ==
  287. Using packaged VIIPER 0.1.5-rc4.6 x64 binary.
  288. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  289. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  290. Disabled existing VIIPER startup until setup verifies the driver ABI.
  291. VIIPER installed to C:\Program Files\DS4Windows\VIIPER\viiper.exe
  292. Windows Installer managed DS4Windows copy and startup target: C:\Program Files\DS4Windows\DS4Windows.exe
  293. Protected elevated VIIPER startup executable: C:\Program Files\DS4Windows\VIIPER\viiper.exe
  294. Protected elevated DS4Windows startup executable: C:\Program Files\DS4Windows\DS4Windows.exe
  295. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  296.  
  297. == Step 2 of 4 - Checking usbip-win2 0.9.7.7 ==
  298. usbip-win2 is unsupported (0.9.8.0); installing or repairing 0.9.7.7.
  299.  
  300. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  301. Setup could not finish: The exact usbip-win2 AppId record has unexpected package identity metadata. No driver transition was started.
  302. Details were saved to C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  303.  
  304.  
  305. 2026-09-19T17:14:16.2962467-05:00 Infrastructure setup exited with code 1. Detailed log: C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  306. 2026-09-19T17:14:16.2972679-05:00 === DS4Windows setup invocation 45d9d2fb9c3342a3904c24cbbb6d2e55 completed with exit code 1 ===
  307. 2026-09-19T17:15:53.4666784-05:00 === DS4Windows setup invocation 9da808876e04493586dc8b9c9b81ba99 started ===
  308. 2026-09-19T17:15:53.4867244-05:00 === DS4Windows setup invocation 9da808876e04493586dc8b9c9b81ba99 completed with exit code 0 ===
  309. 2026-09-19T17:15:58.0995768-05:00 === DS4Windows setup invocation 9da808876e04493586dc8b9c9b81ba99 started ===
  310. 2026-09-19T17:15:58.1208925-05:00 Infrastructure setup starting for interactive user AJ\antio (S-1-5-21-2418015503-3615739347-2779590200-1001).
  311. 2026-09-19T17:16:04.8812920-05:00 The all-in-one installer owns the cross-session setup mutex through child verification and reboot-resume staging.
  312.  
  313. DS4Windows VIIPER virtual controller setup
  314. Standard: install DS4Windows and VIIPER in Program Files.
  315. Planned order:
  316. 1. Install VIIPER and register both elevated startup tasks.
  317. 2. Verify or install packaged usbip-win2 0.9.7.7.
  318. 3. Verify the startup tasks remain exact and enabled.
  319. 4. Start and verify the local VIIPER API.
  320. USB hub devices may restart during driver replacement, and Windows may require a reboot.
  321. Protected DS4Windows package files from unelevated replacement: C:\Program Files\DS4Windows
  322. Protected VIIPER package files from unelevated replacement: C:\Program Files\DS4Windows\VIIPER
  323.  
  324. Setup authorized; beginning verified installation.
  325.  
  326. == Step 1 of 4 - Installing VIIPER 0.1.5-rc4.6 ==
  327. Using packaged VIIPER 0.1.5-rc4.6 x64 binary.
  328. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  329. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  330. Disabled existing VIIPER startup until setup verifies the driver ABI.
  331. VIIPER installed to C:\Program Files\DS4Windows\VIIPER\viiper.exe
  332. Windows Installer managed DS4Windows copy and startup target: C:\Program Files\DS4Windows\DS4Windows.exe
  333. Protected elevated VIIPER startup executable: C:\Program Files\DS4Windows\VIIPER\viiper.exe
  334. Protected elevated DS4Windows startup executable: C:\Program Files\DS4Windows\DS4Windows.exe
  335. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  336.  
  337. == Step 2 of 4 - Checking usbip-win2 0.9.7.7 ==
  338. usbip-win2 is unsupported (0.9.8.0); installing or repairing 0.9.7.7.
  339.  
  340. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  341. Setup could not finish: The exact usbip-win2 AppId record has unexpected package identity metadata. No driver transition was started.
  342. Details were saved to C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  343.  
  344.  
  345. 2026-09-19T17:16:04.8846354-05:00 Infrastructure setup exited with code 1. Detailed log: C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  346. 2026-09-19T17:16:04.8856274-05:00 === DS4Windows setup invocation 9da808876e04493586dc8b9c9b81ba99 completed with exit code 1 ===
  347. 2026-09-20T12:43:35.7484943-05:00 === DS4Windows setup invocation 103b020b91b0424289da9a3ed887f75a started ===
  348. 2026-09-20T12:43:35.7741186-05:00 === DS4Windows setup invocation 103b020b91b0424289da9a3ed887f75a completed with exit code 0 ===
  349. 2026-09-20T12:43:40.4706932-05:00 === DS4Windows setup invocation 103b020b91b0424289da9a3ed887f75a started ===
  350. 2026-09-20T12:43:40.4923310-05:00 Infrastructure setup starting for interactive user AJ\antio (S-1-5-21-2418015503-3615739347-2779590200-1001).
  351. 2026-09-20T12:43:57.0178541-05:00 The all-in-one installer owns the cross-session setup mutex through child verification and reboot-resume staging.
  352.  
  353. DS4Windows VIIPER virtual controller setup
  354. Standard: install DS4Windows and VIIPER in Program Files.
  355. Planned order:
  356. 1. Install VIIPER and register both elevated startup tasks.
  357. 2. Verify or install packaged usbip-win2 0.9.7.7.
  358. 3. Verify the startup tasks remain exact and enabled.
  359. 4. Start and verify the local VIIPER API.
  360. USB hub devices may restart during driver replacement, and Windows may require a reboot.
  361. Protected DS4Windows package files from unelevated replacement: C:\Program Files\DS4Windows
  362. Protected VIIPER package files from unelevated replacement: C:\Program Files\DS4Windows\VIIPER
  363.  
  364. Setup authorized; beginning verified installation.
  365.  
  366. == Step 1 of 4 - Installing VIIPER 0.1.5-rc4.6 ==
  367. Using packaged VIIPER 0.1.5-rc4.6 x64 binary.
  368. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  369. Verified packaged VIIPER SHA256: 9A334912E26FAC09C6DF17BA75A272A41D871D9BBE14934D06F983E101F3DF3C
  370. Disabled existing VIIPER startup until setup verifies the driver ABI.
  371. VIIPER installed to C:\Program Files\DS4Windows\VIIPER\viiper.exe
  372. Windows Installer managed DS4Windows copy and startup target: C:\Program Files\DS4Windows\DS4Windows.exe
  373. Protected elevated VIIPER startup executable: C:\Program Files\DS4Windows\VIIPER\viiper.exe
  374. Protected elevated DS4Windows startup executable: C:\Program Files\DS4Windows\DS4Windows.exe
  375. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  376.  
  377. == Step 2 of 4 - Checking usbip-win2 0.9.7.7 ==
  378.  
  379. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  380. Setup could not finish: USBIP driver or package artifacts exist, but canonical usbip.exe is missing. Refusing to change a driver whose active imports cannot be inspected safely. Repair or remove USBIP manually, reboot, then run setup again.
  381. Details were saved to C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  382.  
  383.  
  384. 2026-09-20T12:43:57.0207469-05:00 Infrastructure setup exited with code 1. Detailed log: C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  385. 2026-09-20T12:43:57.0214912-05:00 === DS4Windows setup invocation 103b020b91b0424289da9a3ed887f75a completed with exit code 1 ===
  386. 2026-10-05T16:30:23.9793434-05:00 === DS4Windows setup invocation 39def7c791d843bc9e88bd035ffc1028 started ===
  387. 2026-10-05T16:30:24.0045209-05:00 === DS4Windows setup invocation 39def7c791d843bc9e88bd035ffc1028 completed with exit code 0 ===
  388. 2026-10-05T16:30:28.1866287-05:00 === DS4Windows setup invocation 39def7c791d843bc9e88bd035ffc1028 started ===
  389. 2026-10-05T16:30:28.2105920-05:00 Infrastructure setup starting for interactive user AJ\antio (S-1-5-21-2418015503-3615739347-2779590200-1001).
  390. 2026-10-05T16:30:40.7877168-05:00 The all-in-one installer owns the cross-session setup mutex through child verification and reboot-resume staging.
  391.  
  392. DS4Windows VIIPER virtual controller setup
  393. Standard: install DS4Windows and VIIPER in Program Files.
  394. Planned order:
  395. 1. Install VIIPER and register both elevated startup tasks.
  396. 2. Verify or install packaged usbip-win2 0.9.7.7.
  397. 3. Verify the startup tasks remain exact and enabled.
  398. 4. Start and verify the local VIIPER API.
  399. USB hub devices may restart during driver replacement, and Windows may require a reboot.
  400. Protected DS4Windows package files from unelevated replacement: C:\Program Files\DS4Windows
  401. Protected VIIPER package files from unelevated replacement: C:\Program Files\DS4Windows\VIIPER
  402.  
  403. Setup authorized; beginning verified installation.
  404.  
  405. == Step 1 of 4 - Installing VIIPER 0.1.9-rc4.6.6 ==
  406. Using packaged VIIPER 0.1.9-rc4.6.6 x64 binary.
  407. Verified packaged VIIPER SHA256: 9392A49E619E1D9B7956EA4BEDAFD2E74CBF5065C011554E80F756D1524F892B
  408. Verified packaged VIIPER SHA256: 9392A49E619E1D9B7956EA4BEDAFD2E74CBF5065C011554E80F756D1524F892B
  409. Disabled existing VIIPER startup until setup verifies the driver ABI.
  410. VIIPER installed to C:\Program Files\DS4Windows\VIIPER\viiper.exe
  411. Windows Installer managed DS4Windows copy and startup target: C:\Program Files\DS4Windows\DS4Windows.exe
  412. Protected elevated VIIPER startup executable: C:\Program Files\DS4Windows\VIIPER\viiper.exe
  413. Protected elevated DS4Windows startup executable: C:\Program Files\DS4Windows\DS4Windows.exe
  414. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  415.  
  416. == Step 2 of 4 - Checking usbip-win2 0.9.7.7 ==
  417.  
  418. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  419. Setup could not finish: USBIP driver or package artifacts exist, but canonical usbip.exe is missing. Refusing to change a driver whose active imports cannot be inspected safely. Repair or remove USBIP manually, reboot, then run setup again.
  420. Details were saved to C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  421.  
  422.  
  423. 2026-10-05T16:30:40.7905306-05:00 Infrastructure setup exited with code 1. Detailed log: C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  424. 2026-10-05T16:30:40.7911359-05:00 === DS4Windows setup invocation 39def7c791d843bc9e88bd035ffc1028 completed with exit code 1 ===
  425. 2026-10-05T16:31:32.6572196-05:00 === DS4Windows setup invocation d4b2944f072e4c128a79554ed31bb0fd started ===
  426. 2026-10-05T16:31:32.6822768-05:00 === DS4Windows setup invocation d4b2944f072e4c128a79554ed31bb0fd completed with exit code 0 ===
  427. 2026-10-05T16:31:37.2916735-05:00 === DS4Windows setup invocation d4b2944f072e4c128a79554ed31bb0fd started ===
  428. 2026-10-05T16:31:37.3159212-05:00 Infrastructure setup starting for interactive user AJ\antio (S-1-5-21-2418015503-3615739347-2779590200-1001).
  429. 2026-10-05T16:31:47.5295956-05:00 The all-in-one installer owns the cross-session setup mutex through child verification and reboot-resume staging.
  430.  
  431. DS4Windows VIIPER virtual controller setup
  432. Standard: install DS4Windows and VIIPER in Program Files.
  433. Planned order:
  434. 1. Install VIIPER and register both elevated startup tasks.
  435. 2. Verify or install packaged usbip-win2 0.9.7.7.
  436. 3. Verify the startup tasks remain exact and enabled.
  437. 4. Start and verify the local VIIPER API.
  438. USB hub devices may restart during driver replacement, and Windows may require a reboot.
  439. Protected DS4Windows package files from unelevated replacement: C:\Program Files\DS4Windows
  440. Protected VIIPER package files from unelevated replacement: C:\Program Files\DS4Windows\VIIPER
  441.  
  442. Setup authorized; beginning verified installation.
  443.  
  444. == Step 1 of 4 - Installing VIIPER 0.1.9-rc4.6.6 ==
  445. Using packaged VIIPER 0.1.9-rc4.6.6 x64 binary.
  446. Verified packaged VIIPER SHA256: 9392A49E619E1D9B7956EA4BEDAFD2E74CBF5065C011554E80F756D1524F892B
  447. Verified packaged VIIPER SHA256: 9392A49E619E1D9B7956EA4BEDAFD2E74CBF5065C011554E80F756D1524F892B
  448. Disabled existing VIIPER startup until setup verifies the driver ABI.
  449. VIIPER installed to C:\Program Files\DS4Windows\VIIPER\viiper.exe
  450. Windows Installer managed DS4Windows copy and startup target: C:\Program Files\DS4Windows\DS4Windows.exe
  451. Protected elevated VIIPER startup executable: C:\Program Files\DS4Windows\VIIPER\viiper.exe
  452. Protected elevated DS4Windows startup executable: C:\Program Files\DS4Windows\DS4Windows.exe
  453. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  454.  
  455. == Step 2 of 4 - Checking usbip-win2 0.9.7.7 ==
  456.  
  457. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  458. Setup could not finish: USBIP driver or package artifacts exist, but canonical usbip.exe is missing. Refusing to change a driver whose active imports cannot be inspected safely. Repair or remove USBIP manually, reboot, then run setup again.
  459. Details were saved to C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  460.  
  461.  
  462. 2026-10-05T16:31:47.5336937-05:00 Infrastructure setup exited with code 1. Detailed log: C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  463. 2026-10-05T16:31:47.5349945-05:00 === DS4Windows setup invocation d4b2944f072e4c128a79554ed31bb0fd completed with exit code 1 ===
  464. 2026-10-05T16:35:51.6537760-05:00 === DS4Windows setup invocation bd702284be2b4edd8e150c79c7ced414 started ===
  465. 2026-10-05T16:35:51.6778940-05:00 === DS4Windows setup invocation bd702284be2b4edd8e150c79c7ced414 completed with exit code 0 ===
  466. 2026-10-05T16:35:56.3357946-05:00 === DS4Windows setup invocation bd702284be2b4edd8e150c79c7ced414 started ===
  467. 2026-10-05T16:35:56.3605388-05:00 Infrastructure setup starting for interactive user AJ\antio (S-1-5-21-2418015503-3615739347-2779590200-1001).
  468. 2026-10-05T16:36:05.6855980-05:00 The all-in-one installer owns the cross-session setup mutex through child verification and reboot-resume staging.
  469.  
  470. DS4Windows VIIPER virtual controller setup
  471. Standard: install DS4Windows and VIIPER in Program Files.
  472. Planned order:
  473. 1. Install VIIPER and register both elevated startup tasks.
  474. 2. Verify or install packaged usbip-win2 0.9.7.7.
  475. 3. Verify the startup tasks remain exact and enabled.
  476. 4. Start and verify the local VIIPER API.
  477. USB hub devices may restart during driver replacement, and Windows may require a reboot.
  478. Protected DS4Windows package files from unelevated replacement: C:\Program Files\DS4Windows
  479. Protected VIIPER package files from unelevated replacement: C:\Program Files\DS4Windows\VIIPER
  480.  
  481. Setup authorized; beginning verified installation.
  482.  
  483. == Step 1 of 4 - Installing VIIPER 0.1.9-rc4.6.6 ==
  484. Using packaged VIIPER 0.1.9-rc4.6.6 x64 binary.
  485. Verified packaged VIIPER SHA256: 9392A49E619E1D9B7956EA4BEDAFD2E74CBF5065C011554E80F756D1524F892B
  486. Verified packaged VIIPER SHA256: 9392A49E619E1D9B7956EA4BEDAFD2E74CBF5065C011554E80F756D1524F892B
  487. Disabled existing VIIPER startup until setup verifies the driver ABI.
  488. VIIPER installed to C:\Program Files\DS4Windows\VIIPER\viiper.exe
  489. Windows Installer managed DS4Windows copy and startup target: C:\Program Files\DS4Windows\DS4Windows.exe
  490. Protected elevated VIIPER startup executable: C:\Program Files\DS4Windows\VIIPER\viiper.exe
  491. Protected elevated DS4Windows startup executable: C:\Program Files\DS4Windows\DS4Windows.exe
  492. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  493.  
  494. == Step 2 of 4 - Checking usbip-win2 0.9.7.7 ==
  495.  
  496. Failure containment preserved foreign same-name task 'RunDS4Windows'.
  497. Setup could not finish: USBIP driver or package artifacts exist, but canonical usbip.exe is missing. Refusing to change a driver whose active imports cannot be inspected safely. Repair or remove USBIP manually, reboot, then run setup again.
  498. Details were saved to C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  499.  
  500.  
  501. 2026-10-05T16:36:05.6896198-05:00 Infrastructure setup exited with code 1. Detailed log: C:\ProgramData\DS4Windows\Installer\infrastructure-actions.log
  502. 2026-10-05T16:36:05.6908931-05:00 === DS4Windows setup invocation bd702284be2b4edd8e150c79c7ced414 completed with exit code 1 ===
  503.  
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!