Divinity: Original Sin 2
Generally, the Debug_Client_Profile_1 profile is created if you start the game again when it is already running (to test something in co-op on a single computer, or create multiple custom party members).
If you click on Profiles in the main menu, can you select the original profile (left click or the up/down arrow keys), so the text colour turns red, then switch by clicking the Select button or hitting Enter?
Can you create a new profile and switch to that? If so, can you then change back to your original profile?
If you can create a new profile, you could just move all your saves over from the original profile’s savegames folder.
If you exit out of the game, you can manually delete the ‘Debug_Client_Profile_1’ profile folder in the ‘..DocumentsLarian StudiosDivinity Original Sin 2PlayerProfiles’ folder.
If that doesn’t help, try browsing to the ‘..DocumentsLarian Studios’ folder and rename the ‘Divinity Original Sin 2’ subfolder.
That will get the game to recreate it on startup, and you should be prompted to create a new profile, after which you can exit and move the saves from your original profile’s savegames folder to the newly created one.
For first question, I can click it, but when clicking select, it doesnt respond. I can create a new profile and switch to that, but when I connect to the old profile it auto switches me to the debug client profile. and thats a good fix for the savegame idea.
after my CTD, my steam got really wierd and slow, so i turned my Pc on and off. when it turned back on, before steam even opened. Divinity was back on in the taskmanager processes. so I turned on steam and logged in and couldnt get into the old profile again, steam was still running SUPER slow after the CTD to. so I looked up how to fix slow steam so i could try fixing divinity again.
Wierd part? The fix for steam was to delete my web browser cache and steam sped back up and when i launched divinity, the default profile was gone, my original profile was accessible and I had my saves back.
Hmm what? lol i mean, its working and fixed but. kind of not how i expected to fix it
- divinity original sin 2 Debug
If you have been playing Divinity Original Sin 2 and have recently had an unexpected crash, there’s a chance your profile may be affected by ‘Debug_Client_Profile_1’ error. It’s also possible to get this error if you have tried to launch more than one instance of Divinity from your Steam account. Thankfully fixing the error is quite easy and won’t result in your losing your valuable saves.
Video games and bugs are two things that go hand in hand, even after rigorous fine-tuning and beta testing, bugs still sometimes manage to elude developers. Fortunately, on most occasions, developers are quick to fix issues caused by bugs and glitches. Divinity is no exception, with the developers at Larian studios working quickly and efficiently with the community to fix any bug/glitches and errors.
The ‘Debug Client Profile’ error in Divinity Original Sin II is quite a unique error and doesn’t generally occur during normal game use. In most cases, you will only ever see the error message if your game crashes with exceptionally bad timing or if you are trying to run more than one instance.
For example, I recently received this error when I launched my game after an unexpected crash just after a save point. Admittedly, I was trying to minimize the game and open guides in Chrome and YouTube, which caused the crash. Most importantly, you don’t have to worry about your save files being lost, even though your profile has been damaged, your save files are safe and undamaged.
Fixing Debug_Client_Profile_1 Error on Divinity Original Sin 2.
Fixing Debug Client Profile error on Divinity is actually a lot easy than you might think and doesn’t require you to do anything drastic. To begin, open Divinity Original Sin as you normally would, then when you have the game open on the main screen, create a new profile.
Make sure you name this new profile something different to the profile that has been damaged.
Once this is done, Exit the game and close Steam. Next, open the Windows File Explorer and navigate to the following location:
Note: Depending on your user account setup for Windows the location may vary slightly. Basically, you are looking for the Savegames folder in the Divinity Original Sin 2 directory in My Documents.
Once you find the Savegames folder, right-click on it, select Copy, then Paste it into the Player Profile folder with the name you created earlier. If it asks you to overwrite any files, choose Yes. As soon as this is done, you can close the File Explorer window and relaunch Divinity.
When you have the game open, select the new profile you made in the first step, then click Continue. This new profile will load your old save data and you will be back in the same location you last saved. It will also contain all the old save data, including any and all quick/autosaves. This method will work for any and all Debug_client_Profile_ errors, regardless of the number that follows them.
A debugging toolset built on Web Services on Devices API (WSDAPI) is available in the Windows SDK and the Windows Driver Kit (WDK). These tools can be used to test the functionality of custom applications written on WSDAPI, or devices and clients written using other Device Profile for Web Services (DPWS) stacks.
The WSD Debug Host (wsddebug_host.exe) and WSD Debug Client (wsddebug_client.exe) tools can be used to inspect the characteristics of DPWS clients or hosts. They can also be used to troubleshoot connectivity or configuration problems. For more information, see WSDAPI Troubleshooting Gu >Bin.
The WSDAPI Basic Interoperability Tool (WSDBIT) can be used to test SOAP-level or transport-level interoperability (that is, ensuring messages are well-formed). This tool is only available in the WDK.
The WSD Debug Client
The WSD Debug Client (wsddebug_client.exe) provides an interactive console that can be used to send and receive WS-Discovery messages, and to obtain metadata. It can also be used to generate and consume raw multicast messages.
The WSD Debug Client operates in one of three modes: multicast, discovery, and metadata.
|Multicast||In Multicast mode, the WSD Debug Client sends and receives unformatted multicast messages on UDP port 3702, as defined in WS-Discovery. The user may save these SOAP messages in a text file, and may modify and rebroadcast the messages with the WSD Debug Client.|
|Discovery||In Discovery mode, the WSD Debug Client sends and receives formatted WS-Discovery messages. It can display received Hello, Bye, ProbeMatches, and ResolveMatches messages. It can send Probe messages over UDP or HTTP, and Resolve messages over UDP.|
|Metadata||In addition to implementing all of the features of Discovery mode, Metadata mode also attempts to retrieve metadata from devices.|
The WSD Debug Host
The WSD Debug Host (wsddebug_host.exe) provides an interactive console used to announce the host, respond to client requests, and print diagnostic information.
The WSD Debug Host operates in one of two modes: discovery and metadata.