Проблемы Pds.exe часто возникают из-за того, что исполняемый файл отсутствует, удалён или перемещён из исходного местоположения. Часто такие EXE ошибки наблюдаются при запуске программного обеспечения Visual Studio Industry Partner Program Partner Resource DVD. Для устранения неполадок, связанных с файлом EXE, большинство профессионалов ПК заменят файл на соответствующую версию. Кроме того, регулярная очистка и оптимизация реестра Windows предотвратит создание неправильных ссылок на пути к файлам EXE, поэтому мы настоятельно рекомендуем регулярно выполнять сканирование реестра.
EXE файлы — это типы Исполнимые файлы, более широко известные в качестве формата Windows Executable File. Мы подготовили для вас несколько версий файлов pds.exe, которые походят для %%os%% и нескольких выпусков Windows. Данные файлы можно посмотреть и скачать ниже. В некоторых случаях в настоящее время в нашей базе могут отсутствовать некоторые версии pds.exe, но их можно запросить, нажав на кнопку Request (Запрос) ниже. Если вы не можете найти нужную версию файла в нашей базе данных, вы также можете обратиться за дополнительной помощью к Microsoft Corporation.
Размещение вновь загруженного файла pds.exe в правильном каталоге (в месте расположения исходного файла), скорее всего, решит проблему, однако, чтобы однозначно в этом убедиться, следует выполнить проверку. Повторно запустите Visual Studio Industry Partner Program Partner Resource DVD, чтобы убедиться, что проблема успешно решена.
pds.exe Описание файла | |
---|---|
Ext: | EXE |
Группа: | Application development |
Program: | Visual Studio Industry Partner Program Partner Resource DVD |
Версия программного обеспечения: | 2007 |
Создано: | Microsoft Corporation |
File: | pds.exe |
Размер (в байтах): | 114688 |
SHA-1: | d812c06a630622868c6279bfd05e7c1a100c8eb1 |
MD5: | 42ec3352a08087eff3e8af87306d7554 |
CRC32: | ada69d79 |
Продукт Solvusoft
Загрузка
WinThruster 2023 — Сканировать ваш компьютер на наличие ошибок реестра в pds.exe
Windows
11/10/8/7/Vista/XP
Установить необязательные продукты — WinThruster (Solvusoft) | Лицензия | Политика защиты личных сведений | Условия | Удаление
EXE
pds.exe
Идентификатор статьи: 851609
Pds.exe
Имя файла | ID | Размер | Загрузить | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
+ pds.exe | 42ec3352a08087eff3e8af87306d7554 | 112.00 KB | ||||||||||||||||
|
||||||||||||||||||
+ pds.exe | 42ec3352a08087eff3e8af87306d7554 | 112.00 KB | ||||||||||||||||
|
||||||||||||||||||
+ pds.exe | 42ec3352a08087eff3e8af87306d7554 | 112.00 KB | ||||||||||||||||
|
pds.exe Проблемы, связанные с Visual Studio Industry Partner Program Partner Resource DVD:
- «Ошибка в приложении: pds.exe»
- «Недопустимая программа Win32: pds.exe»
- «Pds.exe столкнулся с проблемой и закроется. «
- «Pds.exe не может быть найден. «
- «Pds.exe не может быть найден. «
- «Ошибка запуска программы: pds.exe.»
- «Pds.exe не работает. «
- «Pds.exe остановлен. «
- «Pds.exe: путь приложения является ошибкой. «
Обычно ошибки pds.exe с Visual Studio Industry Partner Program Partner Resource DVD возникают во время запуска или завершения работы, в то время как программы, связанные с pds.exe, выполняются, или редко во время последовательности обновления ОС. Запись ошибок pds.exe внутри Visual Studio Industry Partner Program Partner Resource DVD имеет решающее значение для обнаружения неисправностей электронной Application development и ретрансляции обратно в Microsoft Corporation для параметров ремонта.
Истоки проблем Pds.exe
Проблемы Pds.exe могут быть отнесены к поврежденным или отсутствующим файлам, содержащим ошибки записям реестра, связанным с Pds.exe, или к вирусам / вредоносному ПО.
В основном, осложнения pds.exe связаны с:
- Поврежденная или недопустимая запись реестра pds.exe.
- Зазаражение вредоносными программами повредил файл pds.exe.
- Pds.exe злонамеренно или ошибочно удален другим программным обеспечением (кроме Visual Studio Industry Partner Program Partner Resource DVD).
- Другое программное обеспечение, конфликтующее с Visual Studio Industry Partner Program Partner Resource DVD, pds.exe или общими ссылками.
- Поврежденная установка или загрузка Visual Studio Industry Partner Program Partner Resource DVD (pds.exe).
picette
Newbie Posts: 11 Thank You |
Hi, hope this is the correct place. I have been using PDS (3.5.6.7) with Proteus 7. I have just installed Proteus 8, but I am unable to integrate it with Proton Development Suite, as it requires the location of ISIS.EXE and Proteus 8 has a single file (PDS.EXE). If I rename the Proteus 8 PDS.EXE to ISIS.EXE I get an error from Proton about command line errors in the .ini file. Has anyone got Proteus 8 to run from Proton? picette |
||
|
towlerg
Senior Member Posts: 263 Thank You What is this for? |
I don’t beleive it’s possible, with Proteus 8, to use the «compile and program» button to go directly to Proteus (for the reasons you give). Nor is it possible to use the Proton compiler as the project compiler from within Proteus. You still can still declare the .BAS as the program file for the target processor and debug it. Or alternately tell Proton to produce a COF file and use it in Proteus. If you are not welded to Proton but wish to stick with Basic, there is a utility for PICBasic. It was written by Darrel Taylor (that name again) and it allows you to declare PICBasic as the project compiler. Hope that helps George |
||
Win 7 Ult x64 SP1 on HP2570p |
picette
Newbie Posts: 11 Thank You |
Thanks for the quick response. Guess I’ll stick with Proteus 7 for a while. picette |
||
|
pickit2
Moderator Posts: 4583 Thank You There is no evidence that I muted SoNsIvRi |
This should work if you have Proteus open and your set your file location to that of Proton. |
||
Note: I stoped Muteing bad members OK I now put thier account in sleep mode |
towlerg
Senior Member Posts: 263 Thank You What is this for? |
You can get around the problem of having no .HEX file in the event of failed compile, by using Keep_Hex_File as in «Declare Keep_Hex_File = On». Also handy if you use the auto input hex option on PicKit2. George |
||
Win 7 Ult x64 SP1 on HP2570p |
towlerg
Senior Member Posts: 263 Thank You What is this for? |
Just out of curiosity I played with the PICBasic to Proteus 8 loader (is that the right term?) looks like it creates 3 files, one of which is just a program template. I have no notion of the level of difficulty of making the necesary changes for Proton. I must admit that the facility to display selected active portions of the curcuit on the source editing/debugging page seem pretty neat. You should fire up PICBasic and give it a go. George |
||
Win 7 Ult x64 SP1 on HP2570p |
chicowood
Junior Member Posts: 92 Thank You |
Just out of curiosity I played with the PICBasic to Proteus 8 loader (is that the right term?) looks like it creates 3 files, one of which is just a program template. I have no notion of the level of difficulty of making the necesary changes for Proton. I must admit that the facility to display selected active portions of the curcuit on the source editing/debugging page seem pretty neat. You should fire up PICBasic and give it a go. I was browsing this thread and it prompted me to try the PICBasic to Proteus 8 Loader you you posted (in the past I’ve used the MPLAB IDE to build PBP projects with Proteus simulating in a window), but I’m not sure how to use the file you posted. Can you explain how to do so? Thanks… |
||
|
towlerg
Senior Member Posts: 263 Thank You What is this for? |
Sorry, my fault for the confusion. I posted the files that the PICBasic loader seems to be writing to Proteus 8 in the hope that some bright bastard would convert them for Proton. The PICBasic loader package is available on the PICBasic web site, http://support.melabs.com/DT/Proteus_PBP3/PBP3-Proteus8_setup_16.exe George |
||
Win 7 Ult x64 SP1 on HP2570p |
chicowood
Junior Member Posts: 92 Thank You |
I haven’t done much PBP lately so I was saddened to hear of Darrel Taylor’s passing when I went to melabs.com. I’ve used some of his stuff (like DT Interrupts and his LCD bar graph routines). He was a good guy, always very helpful to everyone on the melabs forums. Regarding the PICBasic loader: I’ve installed it on Proteus 8, but am having an issue. As you said, it creates a PBP Program Template file, which compiles and runs correctly. But whenever I add source files to the project (.PBP, .BAS or .INC), they can’t be found so I get errors. For some reason the generated compiler command line doesn’t properly reference the location of the files I’ve specified. Have you successfully used PBP with Proteus 8 in this manner? |
||
|
towlerg
Senior Member Posts: 263 Thank You What is this for? |
Yes, it just worked first time. Compile of the standard program produces this — PBPX.exe -K# -oq -x -P18F4550 -ampasmwin -e»main.err» «..main.PBP» What error do you get? I don’t use PICBasic much or indeed at all, didn’t like the way you couldn’t specify the device in the source and none of the neat add-ons. Apparently Darrel was quite young, which is sad. George |
||
Win 7 Ult x64 SP1 on HP2570p |
chicowood
Junior Member Posts: 92 Thank You |
Yes, it just worked first time. Compile of the standard program produces this — When I use the same standard program, I get the same successful compile that you got. If I leave the main.PBP program in place but paste my own source code over the blinky code, it compiles ok. But I can’t use that technique when there are include files involved. When I add a different source file from the source menu, which is located in the same folder as the Proteus schematic and project file, it can’t find the source file, and compiles with errors. PBPX.exe -K# -oq -x -P16F876A -ampasmwin -e»LCT_TEST.err» «..LCT_TEST.PBP» Error code 2 WARNING: Unable to open INCLUDE file GATE ALARM ICD2.INC. I may have overlooked a setup setting somewhere, but I can’t seem to find it. I looked in the XML file that Darrel’s program created and couldn’t see where the input file specification came from (must be somewhere within Proteus itself). Just wondering if you had tried a different input file and had success. |
||
|
towlerg
Senior Member Posts: 263 Thank You What is this for? |
I tried the example file SOUND.PBP which has an include and that compiled OK and produced a .cof. can you infer anything from the errors? were they generated as a result of the unfound include or something more suspicious? George |
||
Win 7 Ult x64 SP1 on HP2570p |
chicowood
Junior Member Posts: 92 Thank You |
I tried the example file SOUND.PBP which has an include and that compiled OK and produced a .cof. can you infer anything from the errors? were they generated as a result of the unfound include or something more suspicious? Thanks for trying that. It’s helpful. I tried the same file, and it compiles ok as well. But when I try one of my previous .bas or .pbp files, which were edited and saved under MPLAB 7, I get the error shown in the attached screen grab. It’s not location specific, because I get the same error if I copy the file to the location where SOUND.PBP resides and load it from there. So it must have something to do with the file attributes itself. When I double click the file it loads in NotePad like I’d expect, but SOUND.PBP does not. Any ideas? |
||
|
chicowood
Junior Member Posts: 92 Thank You |
A bit of progress, but not there yet… I can get the PBP compiler to attempt to compile the source file I point it to, but it fails to open any of the include files specified. For example, my source code contains the lines: INCLUDE «GATE_ALARM_ICD2.INC» ; timing values for ROM & ICD2 …and I’ve added those files to the file list on the left, but the errors I get are: WARNING: Unable to open INCLUDE file GATE_ALARM_ICD2.INC. I’ve tried renaming the include files with the extensions .pbp and .bas with no luck. It’s gotta be something with the path specification. Proteus doesn’t seem to be looking in the project folder where I told it the files reside. I haven’t yet figured out how to work around whatever the issue is… |
||
|
towlerg
Senior Member Posts: 263 Thank You What is this for? |
So it must have something to do with the file attributes itself. When I double click the file it loads in NotePad like I’d expect, but SOUND.PBP does not. Any ideas? Don’t know if it helps but on my machine the extension .PBP is NOT registered to PICBasic. When time allows I’ll have another play with it. George Edit. I have successfully compiled one of Darrel’s examples with an include, 12-bitDEMO.pbp Sequence I used — Let me know if you want me to try something else. |
||
Win 7 Ult x64 SP1 on HP2570p |
chicowood
Junior Member Posts: 92 Thank You |
Edit. I have successfully compiled one of Darrel’s examples with an include, 12-bitDEMO.pbp George, thanks for staying with me on this. I followed your steps exactly (I think). Both .pbp files have been added to the project. I still get the error on the include files, so either we’re doing something differently or there’s something funky with my setup. Here’s my error message: PBPX.exe -K# -oq -x -P16C62B -ampasmwin -e»DT_Analog.err» «..DT_Analog.pbp» Error code 2 WARNING: Unable to open INCLUDE file DT_ANALOG.PBP. I put the source and include files in a folder on the desktop. Was your include file in the same location as the source file? You told me earlier that you successfully compiled the example file SOUND.PBP, which had an include file, BS1DEFS.BAS. That file also compiled ok for me, HOWEVER the include file BS1DEFS.BAS is NOT in the same folder as SOUND.PBP, it’s in the PBP program folder, C:PBP. So I tried copying the include file to the same folder as SOUND.PBP and renamed it to BS1DEFS2.BAS, and changed the line in the source file to «include BS1DEFS2.BAS». It wouldn’t compile because it couldn’t find the include file. So thus far I’m baffled: if the include file is in the same folder as the source file, the Proteus/PBP Loader can’t find it. Can you shed any light on what I’m seeing? |
||
|
towlerg
Senior Member Posts: 263 Thank You What is this for? |
I assume Proteus finds and is able to display all the files required for the project? and they compile ok in the PICBasic IDE? Yes, the .php and any included are in the same directory — but if they’re user (as opposed to system) include files, don’t they have to be. George |
||
Win 7 Ult x64 SP1 on HP2570p |
chicowood
Junior Member Posts: 92 Thank You |
I assume Proteus finds and is able to display all the files required for the project? and they compile ok in the PICBasic IDE? Proteus displays the files ok, it’s just that on my system the PBP compile fails because it appears the PBP compiler doesn’t correctly reference the .include file location as passed to it by Proteus. But since it works ok on your system, that tells me that I need to dig deeper into my system and see why this is happening. I don’t use the PicBasic IDE. I’ve always used the MPLAB IDE because it is required for the ICD2 hardware debugger, and it also offered nice windowed integration with Proteus 7. But MicroChip stopped development on MPLAB 7 moved to the MPLABX IDE, which I dislike intensely because of it’s poor performance and instability, and it also works poorly with Proteus…lots of lockups and restarts required. MicroChip also stopped support of the ICD2 with MPLABX, supporting only the ICD3, which I own but have issues with as well. So in the past I had a very nice development setup with the ICD2, MPLAB 7 and Proteus 7, but since all of those components have been retired my development system is much less enjoyable to use. Sigh. That’s why I was exploring the Proteus 8 code editing capability, to see if it could be relied upon to work reliably and in an enjoyable fashion. I’d still have to move my project back to MPLABX to use the ICD3, but I’d rather do my initial development and debugging in an environment I enjoy more than MPLABX. My first experiment was to get my legacy PBP files to compile and work under Proteus 8, hence my efforts detailed in this thread. If I can get PBP to compile as it should, I’ll give my C projects a try as well, then decide if it’s worth doing code development using the Proteus 8 system. So that’s my story…if I figure out the PBP issue, I’ll post back. Thanks for your help, George, it lets me know that the issue isn’t universal, which gives me a better starting point… chico |
||
|
towlerg
Senior Member Posts: 263 Thank You What is this for? |
I really don’t know what to suggest, normally I’d say something glib (but often correct) like reinstall but I don’t think that’s going to help. I know that Proteus does not use the PICBasic IDE but I’d try to get that working (just as a start point). Stating the obvious, you need to see the command line that Proteus is calling the PICBasic compiler. As I said, anything I can try, let me know. BTW what C do you use? George Edit. Good or bad news depending on your viewpoint. I tried to create a new project and now I’m getting similar errors to yours. This thing seems a bit tricky. I’ll be back. YA Edit. I am defeated by the logic of this thing. Every time I have a working method, I try a different example and that fails. The only things that seem to consistently work is — a. use as many defaults as possible (name location etc.) then when it works use «save project as» to where you’re source is. I don’t know if this is relevant but only the extension .pbp and .bas are specified as source in the compiler definition file. |
||
Win 7 Ult x64 SP1 on HP2570p |
chicowood
Junior Member Posts: 92 Thank You |
BTW what C do you use? Typically I use the Microchip XC compilers. I’m set up to use BoostC and HighTech compilers for legacy projects. Good or bad news depending on your viewpoint. I tried to create a new project and now I’m getting similar errors to yours. This thing seems a bit tricky. I’ll be back. YA Edit. I am defeated by the logic of this thing. Every time I have a working method, I try a different example and that fails. The only things that seem to consistently work is — a. use as many defaults as possible (name location etc.) then when it works use «save project as» to where you’re source is. I don’t know if this is relevant but only the extension .pbp and .bas are specified as source in the compiler definition file. Yeah, I haven’t figured out the logic yet either. I can open a simple .pbp file in the PBP Examples folder, like «BLINK.PBP», and it compiles fine. But if I move a different .pbp file of my own into the same folder, the PBP compiler (as setup by Proteus) can’t seem to find it. I think it might have something to do with Proteus setting up a temp working directory for the project debugging, and not updating it correctly. Here’s one of the error messages I get: > File ‘C:/Users/JDUNCA~1/AppData/Local/Temp/96a348bea3544f0889040dc44ad74fd2/PIC16F876A/Debug/%INFILE_NAME%.cof’ not found I’ve looked at the PBP.XML file created by Darrel Taylor but can’t see much that would affect this. Darrel must have been working with the Proteus people when he wrote this so he’d have the necessary interface info and know what was happening on the Proteus side of the interface. Sad that he’s not around to query about this; he was always very willing to help. I’ll keep puttering. Please let me know if you find a setup technique that gives consistent results…thanks. chico |
||
|
Contents
- 1. What is PDS.EXE?
- 2. Is PDS.EXE safe, or is it a virus or malware?
- 3. Can I remove or delete PDS.EXE?
- 4. Common PDS.EXE error messages
- 5. How to fix PDS.EXE
- 6. April 2023 Update
- 7. Download or reinstall PDS.EXE
Updated April 2023: Here are three steps to using a repair tool to fix exe problems on your computer: Get it at this link
- Download and install this software.
- Scan your computer for exe problems.
- Repair the exe errors with software tool
PDS.EXE is an executable file that is part of the Proteus 8 Professional program developed by Labcenter Electronics. The software is usually about 646.88 KB in size.
The .exe extension of a file name displays an executable file. In some cases, executable files can damage your computer. Please read the following to decide for yourself whether the PDS.EXE file on your computer is a virus or trojan horse that you should delete, or whether it is a valid Windows operating system file or a reliable application.
Recommended: Identify PDS.EXE related errors
(optional offer for Reimage — Website | EULA | Privacy Policy | Uninstall)
Is PDS.EXE safe, or is it a virus or malware?
The first thing that will help you determine if a particular file is a legitimate Windows process or a virus, is the location of the executable itself. For example, a process like PDS.EXE should run from C:WindowsInstaller{B8A525DB-6906-4F0C-92D7-33D55345E4E8}ext_1.exe and not elsewhere.
To confirm, open the Task Manager, go to View -> Select Columns and select «Image Path Name» to add a location column to your Task Manager. If you find a suspicious directory here, it may be a good idea to investigate this process further.
Another tool that can sometimes help you detect bad processes is Microsoft’s Process Explorer. Start the program (it does not require installation) and activate «Check Legends» under Options. Now go to View -> Select Columns and add «Verified Signer» as one of the columns.
If the «Verified Signer» status of a process is listed as «Unable to Verify», you should take a moment look at the process. Not all good Windows processes have a Verified Signature label, but neither do any of the bad ones.
The most important facts about PDS.EXE:
- Located in C:Program FilesLabcenter ElectronicsProteus 8 Professional subfolder;
- Publisher: Labcenter Electronics
- Full Path: C:WindowsInstaller{B8A525DB-6906-4F0C-92D7-33D55345E4E8}ext_1.exe
- Help file:
- Publisher URL: www.labcenter.com
- Known to be up to 646.88 KB in size on most Windows;
If you had any difficulties with this executable, you should determine if it’s trustworthy before deleting PDS.EXE. To do this, find this process in Task Manager.
Find its location (it should be in C:Program FilesLabcenter ElectronicsProteus 8 Professional) and compare the size etc with the above facts.
If you suspect that you may be infected with a virus, then you must attempt to fix it immediately. To delete the PDS.EXE virus, you should download and install a full security application like Malwarebytes. Note that not all tools can detect every type of malware, so you may need to try several options before you’re successful.
In addition, the functionality of the virus may itself affect the deletion of PDS.EXE. In this case, you must enable Safe Mode with Networking — a secure environment that disables most processes and loads only the most required services and drivers. When there, you can run a security program and a complete system analysis.
Can I remove or delete PDS.EXE?
You should not delete a safe executable file without a valid reason, as this may affect the performance of any associated programs that use that file. Be sure to keep your software and programs up to date to avoid future problems caused by corrupted files. With regard to software functionality issues, check driver and software updates more often, so there is little or no risk of such problems occurring.
According to various sources online,
6% of people remove this file, so it may be harmless, but it is recommended that you check the trustworthiness of this executable yourself to determine if it is safe or a virus. The best diagnosis for these suspicious files is a complete system analysis with Reimage. If the file is classified as malicious, these applications will also delete PDS.EXE and get rid of the associated malware.
However, if it is not a virus and you need to delete PDS.EXE, then you can uninstall Proteus 8 Professional from your computer using its uninstaller, which should be located at: MsiExec.exe /I{B8A525DB-6906-4F0C-92D7-33D55345E4E8}. If you cannot find it’s uninstaller, then you may need to uninstall Proteus 8 Professional to completely delete PDS.EXE. You can use the Add/Remove Program function in the Windows Control Panel.
- 1. In the Start menu (for Windows 8, right-click the screen’s bottom-left corner), click Control Panel, and then under Programs:
o Windows Vista/7/8.1/10: Click Uninstall a Program.
o Windows XP: Click Add or Remove Programs.
- 2. When you find the program Proteus 8 Professional, click it, and then:
o Windows Vista/7/8.1/10: Click Uninstall.
o Windows XP: Click the Remove or Change/Remove tab (to the right of the program).
- 3. Follow the prompts to remove Proteus 8 Professional.
Common PDS.EXE error messages
The most common PDS.EXE errors that can appear are:
• «PDS.EXE Application Error.»
• «PDS.EXE failed.»
• «PDS.EXE has encountered a problem and needs to close. We are sorry for the inconvenience.»
• «PDS.EXE is not a valid Win32 application.»
• «PDS.EXE is not running.»
• «PDS.EXE not found.»
• «Cannot find PDS.EXE.»
• «Error starting program: PDS.EXE.»
• «Faulting Application Path: PDS.EXE.»
These .exe error messages can occur during the installation of a program, during the execution of it’s associate software program, Proteus 8 Professional, during the startup or shutdown of Windows, or even during the installation of the Windows operating system. Keeping a record of when and where your PDS.EXE error occurs is important information when it comes to troubleshooting.
How to fix PDS.EXE
A clean and tidy computer is one of the best ways to avoid problems with Proteus 8 Professional. This means performing malware scans, cleaning your hard disk with cleanmgr and sfc /scannow, uninstalling programs you no longer need, monitoring any auto-start programs (with msconfig), and enabling automatic Windows updates. Don’t forget to always make regular backups or at least define recovery points.
If you have a bigger problem, try to remember the last thing you did or the last thing you installed before the problem. Use the resmon command to identify the processes that are causing your problem. Even in case of serious problems, instead of reinstalling Windows, you should try to repair your installation or, in the case of Windows 8, by executing the command DISM.exe /Online /Cleanup-image /Restorehealth. This allows you to repair the operating system without data loss.
To help you analyze the PDS.EXE process on your computer, you may find the following programs useful: Security Task Manager displays all Windows tasks running, including built-in hidden processes such as keyboard and browser monitoring or auto-start entries. A single security risk rating indicates the probability that it is spyware, malware or a potential Trojan horse. This anti-virus detects and removes spyware, adware, Trojans, keyloggers, malware and trackers from your hard disk.
Updated April 2023:
We recommend you try out this new software that fixes computer errors, protects them from malware and optimizes your PC for performance. This new tool fixes a wide range of computer errors, protects against things like file loss, malware and hardware failures.
- Step 1 : Download PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista – Microsoft Gold Certified).
- Step 2 : Click “Start Scan” to find Windows registry issues that could be causing PC problems.
- Step 3 : Click “Repair All” to fix all issues.
(optional offer for Reimage — Website | EULA | Privacy Policy | Uninstall)
Download or reinstall PDS.EXE
It is not recommended to download replacement exe files from any download sites, as these may themselves contain viruses etc. If you need to download or reinstall PDS.EXE, then we recommend that you reinstall the main application associated with it Proteus 8 Professional.
Operating system information
PDS.EXE errors can occur in any of the following Microsoft Windows operating systems:
- Windows 10
- Windows 8.1
- Windows 7
- Windows Vista
- Windows XP
- Windows ME
- Windows 2000
This file is a part of the Microsoft Windows system. EXE is short for executable and these types of files are used on Windows computers to install or run software.
Some programs may need pds.exe to run properly, so if this file is missing you may encounter issues when trying to launch applications or games. Often, you will get an error message that says “pds.exe missing” that tells you which specific file needs to be restored so that the application or game can continue functioning.
To resolve these issues caused by a missing pds.exe, read the suggestions below.
Author:
Intel Corporation
Process:
CBA — Ping Discovery Service
Part of:
Intel Common Base Agent
Common path(s):
subfolder %SYSTEM%
Filesize(s):
17,920 bytes, 42,744 bytes, 38,696 bytes, 18,944 bytes, 42,776 bytes, 38,648 bytes, 38,680 bytes
How to fix pds.exe missing error?
If the pds.exe missing error appears on your PC, you can use the methods below. Some are automatic, which means you can start a process to let the system automatically restore the file. Others are manual, meaning you will have to manually download pds.exe and move it to the correct program installation folder. If you are not very experienced with digging through system files and would prefer not to, you can simply go straight to an automatic method.
Here our list of solutions to try:
- Method 1: Download pds.exe
- Method 2: Fix the missing pds.exe error automatically
- Method 3: Update drivers to restore missing .exe files
- Method 4: Scan your PC for malware
- Method 5: Use System File Checker (SFC)
- Method 6: Fix corrupted pds.exe file by performing System Restore
Method 1: Download pds.exe
This is the most straightforward approach, but it is fully manual and will require you to download the right exe file and place it in the correct folder on your PC.
Look through the list of available versions of pds.exe then select the correct file and click “Download”. If you are unsure which one to download, read the section below or choose an automatic method.
How to choose the correct version of pds.exe?
When looking through the list of EXE files, pay attention to whether it’s a 64-, or 32-bit file, as well as the language it uses. For 64-bit programs, use 64-bit files if they are listed above.
It’s best to choose those EXE files whose language corresponds to the language of your program, if possible. It’s also recommended to choose the latest version to ensure up-to-date functionality.
As long as you get these two parameters right, you won’t have any issues downloading the right file.
Where to place the pds.exe file?
After you’ve downloaded the correct EXE file, place it inside the program installation folder. Alternatively, you can put the pds.exe file within the Windows system directory.
How to register pds.exe?
If placing the missing pds.exe file into the proper directory doesn’t seem to solve the problem, this means you need to register it. To do so, copy your EXE file to the C:WindowsSystem32 folder, then open a command prompt with administrator privileges. There, type “regsvr32 pds.exe” and press Enter.
Method 2: Fix the missing pds.exe error automatically
Outbyte PC Repair allows you to automatically repair EXE errors, without you having to worry about choosing the right file or registering it. The utility will not only download the correct version of pds.exe for free and suggest the right directory to install it to but will also resolve other issues related to the pds.exe file.
- Download pds.exe
- Fix the missing pds.exe error automatically
- Update drivers to restore missing .exe files
Method 3: Update drivers to restore missing .exe files
Driver updates for the Windows operating system, as well as for network adapters, monitors, printers, etc., can be downloaded individually and installed from the Windows Update Center or by using specialized utilities.
Option 1 — Automatic Device Drivers Update
Outbyte Driver Updater automatically updates drivers on Windows. Routine manual driver updates are now a thing of the past. Just with a few clicks you can automatically search your system for outdated drivers and update all of them.
- Download the Outbyte Driver Updater
- Install the application
- Launch the app
- Driver Updater will scan your system for outdated and missing drivers
- Click Update to automatically update all drivers
Option 2 — Manually Update Device Drivers
Of course, you can also choose to update your drivers yourself one by one. First you will need to look through them to find the outdated ones, then search for the updates online. Here’s how to do that:
- Go to Taskbar’s search box and type Device Manager, then select Device Manager in the search results.
- Select a category to look at the devices’ names — right-click the one that needs to be updated
- Choose Search automatically for updated driver software
- Select Update Driver
- Windows might not be able to find the new driver automatically. In this case, you can find the driver on the manufacturer’s website, where all the necessary instructions are available. Just make sure to find the official website so that you only download the trusted driver and not some malicious software.
Method 4: Scan your PC for malware to fix the pds.exe error
Since EXE files communicate directly with your system to give instructions, they are very common targets for malware, which can intentionally corrupt these files in order to substitute them with its own malicious files. If you suspect that this is what’s causing errors on your system, you should scan your computer for malware and eliminate it as soon as possible.
Option 1 — Windows Defender
The new version of Windows 10 has a built-in application called «Windows Defender», which allows you to check your computer for viruses and remove malware. In order to use the Windows Defender offline scan, follow these steps:
- Press the Win key or click Start and click on the gear icon to open Settings. Alternatively press Win + I key combination.
- Select the Update and Security option and go to the Windows Defender section.
- At the bottom of the Defender settings there is a checkbox labeled «Windows Defender Offline scan». To start it, click «Scan Now». Note that you will have to save all unsaved data before restarting your PC.
After you click the “Scan Now” button, the computer will reboot and automatically start searching for viruses and malware. Upon completion of the scan, the computer will restart, and in the notifications, you will see a report on the completed scan.
Option 2 — Outbyte AVarmor
Outbyte products are some of the most popular and effective programs for dealing with malware and unwanted programs, and they will come in handy even if you have a high-quality third-party antivirus installed. This software is specifically designed to complement your antivirus, not replace it. In the new version of Outbyte, scans can be performed in real time and manually. To initiate a manual scan please follow the steps below:
- Launch Outbyte AVarmor and click the Scan Now button. Also, you can select the Scan option on the left side of the program’s window and click Full Scan. The system will begin scanning and you will be able to see the scan results.
- Select items that you want to quarantine and press the “Quarantine Selected” button. After they’ve been quarantined, you may be prompted to reboot the computer.
- After the program has been restarted, you can delete all quarantined objects by going to the appropriate section of the program. However, if you found that your system started to encounter errors after something was quarantined, you should restore the file instead.
Check your system performance to eliminate file conflicts and junk accumulation. Resolve registry and missing file errors.
Compatible with Windows 7, 8, 10, 11
Method 5: Fix the pds.exe missing error with System File Checker (SFC)
Many users are familiar with the sfc/scannow system file integrity check command, which automatically checks and fixes protected Windows system files. It is often one of the first things experienced Windows users do when they encounter errors.
To execute this command, you have to run Command Prompt as an administrator.
- Start the command line as an administrator in Windows by pressing the Win key on your keyboard and typing «Command Prompt» in the search field, then — right-click on the result and select “Run as administrator”. Alternatively, you can press the Win + X key combination which will open the menu where you can select Command Prompt (Admin).
- Type sfc / scannow while in Command Prompt and hit Enter. After entering the command, a system check will begin. It will take a while, so please be patient. Once the process is complete you will see this message: “Windows Resource Protection found corrupt files and successfully repaired them.” or “Windows Resource Protection found corrupt files but was unable to fix some of them”.
Keep in mind that System File Checker (SFC) cannot fix integrity errors for those system files that are currently being used by the operating system. To fix these files you have to run SFC command through the command prompt in the Windows recovery environment. You can get into Windows Recovery Environment from the login screen by clicking Shutdown, then holding down the Shift key while selecting Restart.
In Windows 10, you can press Win key, select Settings > Update & security > Recovery and under Advanced Startup, click Restart now. You can also boot from the installation disk or bootable USB flash drive with the Windows 10 distribution. On the installation screen select your preferred language and then select “System Restore”. After that, go to “Troubleshooting” > “Advanced Settings” > “Command Prompt”. Once in Command Prompt type the following command: sfc /scannow /offbootdir=C: /offwindir=C:Windows, where C is the partition with the installed operating system and C:Windows, is the path to the Windows 10 folder.
This operation will take a while and it is important to wait until it is complete. When finished, close the command prompt and restart the computer as usual. You should find that the pds.exe missing error is gone.
Method 6: Fix the corrupted pds.exe file by performing a System Restore
System Restore is very useful if you want to fix pds.exe error, or almost any other error. Using the «System Restore» function, you can choose to restore Windows to a date when the pds.exe file was not damaged. Restoring Windows to an earlier date cancels changes that were made to system files since that date. Please follow the steps below to roll back Windows using System Restore and get rid of the pds.exe error.
- Press the Win + R keys combination to launch the Run dialog.
- Type sfc /scannow while in Command Prompt and hit Enter.
After entering the command, a system check will begin. It will take a while, so please be patient. Once the operation is complete you will see this message: “Windows Resource Protection found corrupt files and successfully repaired them.” or “Windows Resource Protection found corrupt files but was unable to fix some of them”.
- Type rstrui in the Run text box and click OK or hit Enter. This will open the system recovery utility.
- The “System Restore” window may include the “Choose a different restore point” option. If so, select this option and click Next. Check the “Show more restore points” checkbox to see a complete list of dates.
- Click the «Next» button and then click «Finish» to confirm your restore point. At this point, your computer will reboot normally and boot up with a restored version of Windows, and the pds.exe error should be resolved.
Process Name: Intel Ping Discovery Service
Author: Intel Corporation.
Download PC Repair Tool & fix pds.exe Windows errors automatically
- System Process:
-
No
- Uses network:
-
No
- Hardware related:
-
No
- Background Process:
-
Yes
- Spyware:
-
No
- Trojan:
-
No
- Virus:
-
No
- Security risk 0-5:
-
0
What is pds exe?
pds.exe is associated with Intel LANDesk Management Suite software and discovers registered products on your computer. This program is a non-essential process, but should not be terminated unless suspected to be causing problems.
The “.exe” file extension stands for Windows executable file. Any program that is executable has the .exe file extension. Find out if pds.exe is a virus and sould be removed, how to fix pds.exe error, if pds exe is CPU intensive and slowing down your Windows PC.
Any process has four stages of the lifecycle including start, ready, running, waiting, terminated or exit.
Should You Remove pds exe?
If you are asking yourself if it is safe to remove pds.exe from your Windows system then it is understandable that it is causing trouble. pds.exe is not a critical component and a non-system process. Any process that is not managed by the system is known as non-system processes. It is safe to terminate the non-system process as they do not affect the general functionality of the operating system. However, the program using the non-system processes will be either terminated or halted.
Download PC Repair Tool & fix pds.exe Windows errors automatically
Fix pds.exe Error?
There are many reasons why you are seeing pds.exe error in your Windows system including:
- Malicious software
- Malicious software infects the system with malware, keyloggers, spyware, and other malicious actors. They slow down the whole system and also cause .exe errors. This occurs because they modify the registry which is very important in the proper functioning of processes.
- Incomplete installation
- Another common reason behind pds.exe error is an incomplete installation. It can happen because of errors during installation, lack of hard disk space, and crash during install. This also leads to a corrupted registry causing the error.
Application conflicts and Missing or corrupt windows drivers can also lead to pds.exe error.
The solution to fixing pds.exe error include any one of the following
- Make sure your PC is protected with proper anti-virus software program.
- Run a registry cleaner to repair and remove the Windows registry that is causing pds.exe error.
- Make sure the system’s device drivers are updated properly.
It is also recommended that you run a performance scan to automatically optimize memory and CPU settings.
Download PC Repair Tool & fix pds.exe Windows errors automatically
Is a pds.exe CPU intensive?
Windows process requires three resource types to function properly including CPU, Memory, and Network. CPU cycles to do computational tasks, memory to store information and network to communicate with the required services. If any of the resources are not available, it will either get interrupted or stopped.
Any given process has a process identification number(PID) associated with it. A user can easily identify and track a process using its PID. Task Manager is a great way to learn how much resources pds.exe process is allocating to itself. It showcases process resource usage in CPU/Memory/Disk and Network. If you have a GPU, it will also showcase the percentage of GPU it is using to run the process.
Similar Windows Process
What is pds.exe?
The genuine pds.exe file is a software component of LANDESK Management Suite by .
«pds.exe» is a file in Windows for the LANDESK Management Suite and the LANDESK Common Base Agent within the suite. It is the ping discovery service executable that is used for remote troubleshooting, remote installations, device discovery and inventories, device usage monitoring, and much more. The file sends and receives pings from remote computers. When it receives a ping, it makes record of it and responds to it if the ping requires an action. LANDESK Software started in 1985 as LAN Systems and was acquired by Intel in 1991, yet the company underwent several ownership transitions, followed by becoming an individual company known as LANDESK Software. They provide worldwide IT solutions and products, designed for business and individual use.
pds stands for ping discovery service
The .exe extension on a filename indicates an executable file. Executable files may, in some cases, harm your computer. Therefore, please read below to decide for yourself whether the pds.exe on your computer is a Trojan that you should remove, or whether it is a file belonging to the Windows operating system or to a trusted application.
Click to Run a Free Scan for pds.exe related errors
Pds.exe file information
The process known as CBA — Ping Discovery Service or Proteus (version 8 Application Framework) belongs to software Intel Common Base Agent or Proteus (version 8 Professional) by LANDesk Software (www.landesk.com) or Intel (www.intel.com).
Description: Pds.exe is not essential for the Windows OS and causes relatively few problems. Pds.exe is located in a subfolder of C:WindowsSystem32 or sometimes in a subfolder of C:Windows—usually C:WindowsSystem32CBA.
Known file sizes on Windows 10/11/7 are 32,825 bytes (58% of all occurrences), 32,819 bytes, 24,627 bytes, 17,920 bytes or 18,944 bytes.
The program is not visible. The pds.exe file is not a Windows system file. The program listens for or sends data on open ports to a LAN or the Internet. Pds.exe is an unknown file in the Windows folder.
Pds.exe is able to hide itself.
Therefore the technical security rating is 66% dangerous, but you should also take into account the user reviews.
Recommended: Identify pds.exe related errors
If pds.exe is located in a subfolder of «C:Program Files», the security rating is 37% dangerous. The file size is 32,825 bytes (66% of all occurrences), 1,229,312 bytes or 1,545,216 bytes.
The pds.exe file is not a Windows core file. The program is not visible. The software uses ports to connect to or from a LAN or the Internet.
Pds.exe is able to hide itself.
External information from Paul Collins:
- «Intel PDS» can run at start up. Intel Ping Discovery Service (PDS). Part of Intel’s LANDesk Management Suite 6 and the Common Base Agent (CBA) — used for communicating between the core server and managed clients. Will start the dial-up if installed and enabled
Important: Some malware camouflages itself as pds.exe, particularly when located in the C:Windows or C:WindowsSystem32 folder. Therefore, you should check the pds.exe process on your PC to see if it is a threat. We recommend Security Task Manager for verifying your computer’s security. This was one of the Top Download Picks of The Washington Post and PC World.
Best practices for resolving pds issues
A clean and tidy computer is the key requirement for avoiding problems with pds. This means running a scan for malware, cleaning your hard drive using 1cleanmgr and 2sfc /scannow, 3uninstalling programs that you no longer need, checking for Autostart programs (using 4msconfig) and enabling Windows’ 5Automatic Update. Always remember to perform periodic backups, or at least to set restore points.
Should you experience an actual problem, try to recall the last thing you did, or the last thing you installed before the problem appeared for the first time. Use the 6resmon command to identify the processes that are causing your problem. Even for serious problems, rather than reinstalling Windows, you are better off repairing of your installation or, for Windows 8 and later versions, executing the 7DISM.exe /Online /Cleanup-image /Restorehealth command. This allows you to repair the operating system without losing data.
To help you analyze the pds.exe process on your computer, the following programs have proven to be helpful: ASecurity Task Manager displays all running Windows tasks, including embedded hidden processes, such as keyboard and browser monitoring or Autostart entries. A unique security risk rating indicates the likelihood of the process being potential spyware, malware or a Trojan. BMalwarebytes Anti-Malware detects and removes sleeping spyware, adware, Trojans, keyloggers, malware and trackers from your hard drive.
Other processes
egdpsvc.exe nsvcip.exe updatebhowin32.dll pds.exe wtclient.exe avkwctlx64.exe coreserviceshell.exe funmoods.dll stdrt.exe avwebgrd.exe jccatch.dll [all]
Спасибо,я понял,вот еще тут нашел- http://radiokot.ru/forum/viewtopic.php?t=3739
Вот еще-
Основная ошибка всех начинающих работать с Протеусом – установка и запуск программы от имени пользователя компьютера, набранного кириллицей. Протеус не дружит с русскими буквами в путях к файлам. Поэтому, если у текущего пользователя имя «Вася», «Мария Ивановна» и т.п. вы рискуете при запуске симуляции получить следующее красное сообщение в окне log:
Cannot open ‘C:DOCUME~1ТЕКПОЛЬЗLocal SettingTempLISAxxx.SDF’
Simulation FAILED due to fatal simulator errors
где вместо ТЕКПОЛЬЗ закорючки. Это объясняется тем, что при запуске симуляции Протеус пытается создать в данной папке свой файл LISAxxx.SDF, но не понимает русские буквы в абсолютном пути. Есть два пути решения этой проблемы:
1)Изменить имя пользователя на английский вариант.
2)Зайти в Мой компьютер=>Свойства=>Дополнительно=>Переменные среды. В верхнем окне, выбрав переменную TEMP, нажать Изменить и вместо %USERPROFILE%
набрать %ALLUSERPROFILE% (при этом необходимо, чтобы в папке Document and SettingAll Users имелись соответствующие папки Local Settings и Temp их можно просто перекопировать из текущего пользователя (папки СКРЫТЫЕ) или создать вручную). Можно по совету Nemo78 изменить путь на %SYSTEMROOT%Temp (именно так без Local Settings), тогда Протеус будет использовать папку TEMP в системном каталоге Windows.
Contents
- 1. What is PDS.EXE?
- 2. Is PDS.EXE safe, or is it a virus or malware?
- 3. Can I remove or delete PDS.EXE?
- 4. Common PDS.EXE error messages
- 5. How to fix PDS.EXE
- 6. June 2023 Update
- 7. Download or reinstall PDS.EXE
Updated June 2023: Here are three steps to using a repair tool to fix exe problems on your computer: Get it at this link
- Download and install this software.
- Scan your computer for exe problems.
- Repair the exe errors with software tool
PDS.EXE is an executable file that is part of the Proteus 8 Professional program developed by Labcenter Electronics. The software is usually about 646.88 KB in size.
The .exe extension of a file name displays an executable file. In some cases, executable files can damage your computer. Please read the following to decide for yourself whether the PDS.EXE file on your computer is a virus or trojan horse that you should delete, or whether it is a valid Windows operating system file or a reliable application.
Recommended: Identify PDS.EXE related errors
(optional offer for Reimage — Website | EULA | Privacy Policy | Uninstall)
Is PDS.EXE safe, or is it a virus or malware?
The first thing that will help you determine if a particular file is a legitimate Windows process or a virus, is the location of the executable itself. For example, a process like PDS.EXE should run from C:WindowsInstaller{B8A525DB-6906-4F0C-92D7-33D55345E4E8}ext_1.exe and not elsewhere.
To confirm, open the Task Manager, go to View -> Select Columns and select «Image Path Name» to add a location column to your Task Manager. If you find a suspicious directory here, it may be a good idea to investigate this process further.
Another tool that can sometimes help you detect bad processes is Microsoft’s Process Explorer. Start the program (it does not require installation) and activate «Check Legends» under Options. Now go to View -> Select Columns and add «Verified Signer» as one of the columns.
If the «Verified Signer» status of a process is listed as «Unable to Verify», you should take a moment look at the process. Not all good Windows processes have a Verified Signature label, but neither do any of the bad ones.
The most important facts about PDS.EXE:
- Located in C:Program FilesLabcenter ElectronicsProteus 8 Professional subfolder;
- Publisher: Labcenter Electronics
- Full Path: C:WindowsInstaller{B8A525DB-6906-4F0C-92D7-33D55345E4E8}ext_1.exe
- Help file:
- Publisher URL: www.labcenter.com
- Known to be up to 646.88 KB in size on most Windows;
If you had any difficulties with this executable, you should determine if it’s trustworthy before deleting PDS.EXE. To do this, find this process in Task Manager.
Find its location (it should be in C:Program FilesLabcenter ElectronicsProteus 8 Professional) and compare the size etc with the above facts.
If you suspect that you may be infected with a virus, then you must attempt to fix it immediately. To delete the PDS.EXE virus, you should download and install a full security application like Malwarebytes. Note that not all tools can detect every type of malware, so you may need to try several options before you’re successful.
In addition, the functionality of the virus may itself affect the deletion of PDS.EXE. In this case, you must enable Safe Mode with Networking — a secure environment that disables most processes and loads only the most required services and drivers. When there, you can run a security program and a complete system analysis.
Can I remove or delete PDS.EXE?
You should not delete a safe executable file without a valid reason, as this may affect the performance of any associated programs that use that file. Be sure to keep your software and programs up to date to avoid future problems caused by corrupted files. With regard to software functionality issues, check driver and software updates more often, so there is little or no risk of such problems occurring.
According to various sources online,
6% of people remove this file, so it may be harmless, but it is recommended that you check the trustworthiness of this executable yourself to determine if it is safe or a virus. The best diagnosis for these suspicious files is a complete system analysis with Reimage. If the file is classified as malicious, these applications will also delete PDS.EXE and get rid of the associated malware.
However, if it is not a virus and you need to delete PDS.EXE, then you can uninstall Proteus 8 Professional from your computer using its uninstaller, which should be located at: MsiExec.exe /I{B8A525DB-6906-4F0C-92D7-33D55345E4E8}. If you cannot find it’s uninstaller, then you may need to uninstall Proteus 8 Professional to completely delete PDS.EXE. You can use the Add/Remove Program function in the Windows Control Panel.
- 1. In the Start menu (for Windows 8, right-click the screen’s bottom-left corner), click Control Panel, and then under Programs:
o Windows Vista/7/8.1/10: Click Uninstall a Program.
o Windows XP: Click Add or Remove Programs.
- 2. When you find the program Proteus 8 Professional, click it, and then:
o Windows Vista/7/8.1/10: Click Uninstall.
o Windows XP: Click the Remove or Change/Remove tab (to the right of the program).
- 3. Follow the prompts to remove Proteus 8 Professional.
Common PDS.EXE error messages
The most common PDS.EXE errors that can appear are:
• «PDS.EXE Application Error.»
• «PDS.EXE failed.»
• «PDS.EXE has encountered a problem and needs to close. We are sorry for the inconvenience.»
• «PDS.EXE is not a valid Win32 application.»
• «PDS.EXE is not running.»
• «PDS.EXE not found.»
• «Cannot find PDS.EXE.»
• «Error starting program: PDS.EXE.»
• «Faulting Application Path: PDS.EXE.»
These .exe error messages can occur during the installation of a program, during the execution of it’s associate software program, Proteus 8 Professional, during the startup or shutdown of Windows, or even during the installation of the Windows operating system. Keeping a record of when and where your PDS.EXE error occurs is important information when it comes to troubleshooting.
How to fix PDS.EXE
A clean and tidy computer is one of the best ways to avoid problems with Proteus 8 Professional. This means performing malware scans, cleaning your hard disk with cleanmgr and sfc /scannow, uninstalling programs you no longer need, monitoring any auto-start programs (with msconfig), and enabling automatic Windows updates. Don’t forget to always make regular backups or at least define recovery points.
If you have a bigger problem, try to remember the last thing you did or the last thing you installed before the problem. Use the resmon command to identify the processes that are causing your problem. Even in case of serious problems, instead of reinstalling Windows, you should try to repair your installation or, in the case of Windows 8, by executing the command DISM.exe /Online /Cleanup-image /Restorehealth. This allows you to repair the operating system without data loss.
To help you analyze the PDS.EXE process on your computer, you may find the following programs useful: Security Task Manager displays all Windows tasks running, including built-in hidden processes such as keyboard and browser monitoring or auto-start entries. A single security risk rating indicates the probability that it is spyware, malware or a potential Trojan horse. This anti-virus detects and removes spyware, adware, Trojans, keyloggers, malware and trackers from your hard disk.
Updated June 2023:
We recommend you try out this new software that fixes computer errors, protects them from malware and optimizes your PC for performance. This new tool fixes a wide range of computer errors, protects against things like file loss, malware and hardware failures.
- Step 1 : Download PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista – Microsoft Gold Certified).
- Step 2 : Click “Start Scan” to find Windows registry issues that could be causing PC problems.
- Step 3 : Click “Repair All” to fix all issues.
(optional offer for Reimage — Website | EULA | Privacy Policy | Uninstall)
Download or reinstall PDS.EXE
It is not recommended to download replacement exe files from any download sites, as these may themselves contain viruses etc. If you need to download or reinstall PDS.EXE, then we recommend that you reinstall the main application associated with it Proteus 8 Professional.
Operating system information
PDS.EXE errors can occur in any of the following Microsoft Windows operating systems:
- Windows 10
- Windows 8.1
- Windows 7
- Windows Vista
- Windows XP
- Windows ME
- Windows 2000
Updated March 2023: Stop getting error messages and slow down your system with our optimization tool. Get it now at this link
- Download and install the repair tool here.
- Let it scan your computer.
- The tool will then repair your computer.
pds.exe is a part of Microsoft® Windows® Operating System program developed by LiberKey.com.Some applications or games may need this file to work properly. If pds.exe is error, whenever you start the application/game you may experience various kinds of errors. To fix those errors, please read the Recommended Solution below:
- Company: LiberKey.com
- Product: LiberKey Portable Desktop Shortcuts
- Version: 0.1.0.56
- MD5: DA046D49D3ED400C28CFA600B532DA60
- Size: 434568.00 Byte
Is pds.exe a virus
The legit pds.exe process is located in the e: liberkey liberkeytools pds folder. If it is located elsewhere, it could be malware as a virus can have any name. Some virus can pretend to be pds.exe and reside in the Windows or the System32 folder. One way to confirm would be to right-click on the file and use anti-virus software to scan it — download anti-virus here
What is pds.exe is error mean?
There are multiple reasons that may cause pds.exe errors. These include Windows registry issues, malicious software, faulty applications, etc.Error messages related to the pds.exe file can also indicate that the file has been incorrectly installed, corrupted or removed.
Other common pds.exe errors include:
- “pds.exe is missing”
- “pds.exe error loading”
- “pds.exe crash”
- “pds.exe was not found”
- “pds.exe could not be located”
- “pds.exe Access Violation”
- “The procedure entry point pds.exe error”
- “Cannot find pds.exe”
- “Cannot register pds.exe”
Recommended Solution to Fix pds.exe error
To quickly resolve your problem, we recommend download and use pds.exe Fix Tool,this tool perform a scan for pds.exe issues and other system errors. It will also check if all .dll and .exe files are registered in the system and scan for other issues that may be preventing system from working properly. After the scan process, it will allow you to repair the errors.
Step 1: Click the “Download Here” button to get an automatic tool.
Step 2: Install the utility by following simple installation instructions.
Step 3: Launch the program to fix your pds.exe errors and other issues.
Download Fix Tool to Remove pds.exe Error
picette
Newbie Posts: 11 Thank You |
Hi, hope this is the correct place. I have been using PDS (3.5.6.7) with Proteus 7. I have just installed Proteus 8, but I am unable to integrate it with Proton Development Suite, as it requires the location of ISIS.EXE and Proteus 8 has a single file (PDS.EXE). If I rename the Proteus 8 PDS.EXE to ISIS.EXE I get an error from Proton about command line errors in the .ini file. Has anyone got Proteus 8 to run from Proton? picette |
||
|
towlerg
Senior Member Posts: 263 Thank You What is this for? |
I don’t beleive it’s possible, with Proteus 8, to use the «compile and program» button to go directly to Proteus (for the reasons you give). Nor is it possible to use the Proton compiler as the project compiler from within Proteus. You still can still declare the .BAS as the program file for the target processor and debug it. Or alternately tell Proton to produce a COF file and use it in Proteus. If you are not welded to Proton but wish to stick with Basic, there is a utility for PICBasic. It was written by Darrel Taylor (that name again) and it allows you to declare PICBasic as the project compiler. Hope that helps George |
||
Win 7 Ult x64 SP1 on HP2570p |
picette
Newbie Posts: 11 Thank You |
Thanks for the quick response. Guess I’ll stick with Proteus 7 for a while. picette |
||
|
pickit2
Moderator Posts: 4596 Thank You There is no evidence that I muted SoNsIvRi |
This should work if you have Proteus open and your set your file location to that of Proton. |
||
Note: I stoped Muteing bad members OK I now put thier account in sleep mode |
towlerg
Senior Member Posts: 263 Thank You What is this for? |
You can get around the problem of having no .HEX file in the event of failed compile, by using Keep_Hex_File as in «Declare Keep_Hex_File = On». Also handy if you use the auto input hex option on PicKit2. George |
||
Win 7 Ult x64 SP1 on HP2570p |
towlerg
Senior Member Posts: 263 Thank You What is this for? |
Just out of curiosity I played with the PICBasic to Proteus 8 loader (is that the right term?) looks like it creates 3 files, one of which is just a program template. I have no notion of the level of difficulty of making the necesary changes for Proton. I must admit that the facility to display selected active portions of the curcuit on the source editing/debugging page seem pretty neat. You should fire up PICBasic and give it a go. George |
||
Win 7 Ult x64 SP1 on HP2570p |
chicowood
Junior Member Posts: 92 Thank You |
Just out of curiosity I played with the PICBasic to Proteus 8 loader (is that the right term?) looks like it creates 3 files, one of which is just a program template. I have no notion of the level of difficulty of making the necesary changes for Proton. I must admit that the facility to display selected active portions of the curcuit on the source editing/debugging page seem pretty neat. You should fire up PICBasic and give it a go. I was browsing this thread and it prompted me to try the PICBasic to Proteus 8 Loader you you posted (in the past I’ve used the MPLAB IDE to build PBP projects with Proteus simulating in a window), but I’m not sure how to use the file you posted. Can you explain how to do so? Thanks… |
||
|
towlerg
Senior Member Posts: 263 Thank You What is this for? |
Sorry, my fault for the confusion. I posted the files that the PICBasic loader seems to be writing to Proteus 8 in the hope that some bright bastard would convert them for Proton. The PICBasic loader package is available on the PICBasic web site, http://support.melabs.com/DT/Proteus_PBP3/PBP3-Proteus8_setup_16.exe George |
||
Win 7 Ult x64 SP1 on HP2570p |
chicowood
Junior Member Posts: 92 Thank You |
I haven’t done much PBP lately so I was saddened to hear of Darrel Taylor’s passing when I went to melabs.com. I’ve used some of his stuff (like DT Interrupts and his LCD bar graph routines). He was a good guy, always very helpful to everyone on the melabs forums. Regarding the PICBasic loader: I’ve installed it on Proteus 8, but am having an issue. As you said, it creates a PBP Program Template file, which compiles and runs correctly. But whenever I add source files to the project (.PBP, .BAS or .INC), they can’t be found so I get errors. For some reason the generated compiler command line doesn’t properly reference the location of the files I’ve specified. Have you successfully used PBP with Proteus 8 in this manner? |
||
|
towlerg
Senior Member Posts: 263 Thank You What is this for? |
Yes, it just worked first time. Compile of the standard program produces this — PBPX.exe -K# -oq -x -P18F4550 -ampasmwin -e»main.err» «..main.PBP» What error do you get? I don’t use PICBasic much or indeed at all, didn’t like the way you couldn’t specify the device in the source and none of the neat add-ons. Apparently Darrel was quite young, which is sad. George |
||
Win 7 Ult x64 SP1 on HP2570p |
chicowood
Junior Member Posts: 92 Thank You |
Yes, it just worked first time. Compile of the standard program produces this — When I use the same standard program, I get the same successful compile that you got. If I leave the main.PBP program in place but paste my own source code over the blinky code, it compiles ok. But I can’t use that technique when there are include files involved. When I add a different source file from the source menu, which is located in the same folder as the Proteus schematic and project file, it can’t find the source file, and compiles with errors. PBPX.exe -K# -oq -x -P16F876A -ampasmwin -e»LCT_TEST.err» «..LCT_TEST.PBP» Error code 2 WARNING: Unable to open INCLUDE file GATE ALARM ICD2.INC. I may have overlooked a setup setting somewhere, but I can’t seem to find it. I looked in the XML file that Darrel’s program created and couldn’t see where the input file specification came from (must be somewhere within Proteus itself). Just wondering if you had tried a different input file and had success. |
||
|
towlerg
Senior Member Posts: 263 Thank You What is this for? |
I tried the example file SOUND.PBP which has an include and that compiled OK and produced a .cof. can you infer anything from the errors? were they generated as a result of the unfound include or something more suspicious? George |
||
Win 7 Ult x64 SP1 on HP2570p |
chicowood
Junior Member Posts: 92 Thank You |
I tried the example file SOUND.PBP which has an include and that compiled OK and produced a .cof. can you infer anything from the errors? were they generated as a result of the unfound include or something more suspicious? Thanks for trying that. It’s helpful. I tried the same file, and it compiles ok as well. But when I try one of my previous .bas or .pbp files, which were edited and saved under MPLAB 7, I get the error shown in the attached screen grab. It’s not location specific, because I get the same error if I copy the file to the location where SOUND.PBP resides and load it from there. So it must have something to do with the file attributes itself. When I double click the file it loads in NotePad like I’d expect, but SOUND.PBP does not. Any ideas? |
||
|
chicowood
Junior Member Posts: 92 Thank You |
A bit of progress, but not there yet… I can get the PBP compiler to attempt to compile the source file I point it to, but it fails to open any of the include files specified. For example, my source code contains the lines: INCLUDE «GATE_ALARM_ICD2.INC» ; timing values for ROM & ICD2 …and I’ve added those files to the file list on the left, but the errors I get are: WARNING: Unable to open INCLUDE file GATE_ALARM_ICD2.INC. I’ve tried renaming the include files with the extensions .pbp and .bas with no luck. It’s gotta be something with the path specification. Proteus doesn’t seem to be looking in the project folder where I told it the files reside. I haven’t yet figured out how to work around whatever the issue is… |
||
|
towlerg
Senior Member Posts: 263 Thank You What is this for? |
So it must have something to do with the file attributes itself. When I double click the file it loads in NotePad like I’d expect, but SOUND.PBP does not. Any ideas? Don’t know if it helps but on my machine the extension .PBP is NOT registered to PICBasic. When time allows I’ll have another play with it. George Edit. I have successfully compiled one of Darrel’s examples with an include, 12-bitDEMO.pbp Sequence I used — Let me know if you want me to try something else. |
||
Win 7 Ult x64 SP1 on HP2570p |
chicowood
Junior Member Posts: 92 Thank You |
Edit. I have successfully compiled one of Darrel’s examples with an include, 12-bitDEMO.pbp George, thanks for staying with me on this. I followed your steps exactly (I think). Both .pbp files have been added to the project. I still get the error on the include files, so either we’re doing something differently or there’s something funky with my setup. Here’s my error message: PBPX.exe -K# -oq -x -P16C62B -ampasmwin -e»DT_Analog.err» «..DT_Analog.pbp» Error code 2 WARNING: Unable to open INCLUDE file DT_ANALOG.PBP. I put the source and include files in a folder on the desktop. Was your include file in the same location as the source file? You told me earlier that you successfully compiled the example file SOUND.PBP, which had an include file, BS1DEFS.BAS. That file also compiled ok for me, HOWEVER the include file BS1DEFS.BAS is NOT in the same folder as SOUND.PBP, it’s in the PBP program folder, C:PBP. So I tried copying the include file to the same folder as SOUND.PBP and renamed it to BS1DEFS2.BAS, and changed the line in the source file to «include BS1DEFS2.BAS». It wouldn’t compile because it couldn’t find the include file. So thus far I’m baffled: if the include file is in the same folder as the source file, the Proteus/PBP Loader can’t find it. Can you shed any light on what I’m seeing? |
||
|
towlerg
Senior Member Posts: 263 Thank You What is this for? |
I assume Proteus finds and is able to display all the files required for the project? and they compile ok in the PICBasic IDE? Yes, the .php and any included are in the same directory — but if they’re user (as opposed to system) include files, don’t they have to be. George |
||
Win 7 Ult x64 SP1 on HP2570p |
chicowood
Junior Member Posts: 92 Thank You |
I assume Proteus finds and is able to display all the files required for the project? and they compile ok in the PICBasic IDE? Proteus displays the files ok, it’s just that on my system the PBP compile fails because it appears the PBP compiler doesn’t correctly reference the .include file location as passed to it by Proteus. But since it works ok on your system, that tells me that I need to dig deeper into my system and see why this is happening. I don’t use the PicBasic IDE. I’ve always used the MPLAB IDE because it is required for the ICD2 hardware debugger, and it also offered nice windowed integration with Proteus 7. But MicroChip stopped development on MPLAB 7 moved to the MPLABX IDE, which I dislike intensely because of it’s poor performance and instability, and it also works poorly with Proteus…lots of lockups and restarts required. MicroChip also stopped support of the ICD2 with MPLABX, supporting only the ICD3, which I own but have issues with as well. So in the past I had a very nice development setup with the ICD2, MPLAB 7 and Proteus 7, but since all of those components have been retired my development system is much less enjoyable to use. Sigh. That’s why I was exploring the Proteus 8 code editing capability, to see if it could be relied upon to work reliably and in an enjoyable fashion. I’d still have to move my project back to MPLABX to use the ICD3, but I’d rather do my initial development and debugging in an environment I enjoy more than MPLABX. My first experiment was to get my legacy PBP files to compile and work under Proteus 8, hence my efforts detailed in this thread. If I can get PBP to compile as it should, I’ll give my C projects a try as well, then decide if it’s worth doing code development using the Proteus 8 system. So that’s my story…if I figure out the PBP issue, I’ll post back. Thanks for your help, George, it lets me know that the issue isn’t universal, which gives me a better starting point… chico |
||
|
towlerg
Senior Member Posts: 263 Thank You What is this for? |
I really don’t know what to suggest, normally I’d say something glib (but often correct) like reinstall but I don’t think that’s going to help. I know that Proteus does not use the PICBasic IDE but I’d try to get that working (just as a start point). Stating the obvious, you need to see the command line that Proteus is calling the PICBasic compiler. As I said, anything I can try, let me know. BTW what C do you use? George Edit. Good or bad news depending on your viewpoint. I tried to create a new project and now I’m getting similar errors to yours. This thing seems a bit tricky. I’ll be back. YA Edit. I am defeated by the logic of this thing. Every time I have a working method, I try a different example and that fails. The only things that seem to consistently work is — a. use as many defaults as possible (name location etc.) then when it works use «save project as» to where you’re source is. I don’t know if this is relevant but only the extension .pbp and .bas are specified as source in the compiler definition file. |
||
Win 7 Ult x64 SP1 on HP2570p |
chicowood
Junior Member Posts: 92 Thank You |
BTW what C do you use? Typically I use the Microchip XC compilers. I’m set up to use BoostC and HighTech compilers for legacy projects. Good or bad news depending on your viewpoint. I tried to create a new project and now I’m getting similar errors to yours. This thing seems a bit tricky. I’ll be back. YA Edit. I am defeated by the logic of this thing. Every time I have a working method, I try a different example and that fails. The only things that seem to consistently work is — a. use as many defaults as possible (name location etc.) then when it works use «save project as» to where you’re source is. I don’t know if this is relevant but only the extension .pbp and .bas are specified as source in the compiler definition file. Yeah, I haven’t figured out the logic yet either. I can open a simple .pbp file in the PBP Examples folder, like «BLINK.PBP», and it compiles fine. But if I move a different .pbp file of my own into the same folder, the PBP compiler (as setup by Proteus) can’t seem to find it. I think it might have something to do with Proteus setting up a temp working directory for the project debugging, and not updating it correctly. Here’s one of the error messages I get: > File ‘C:/Users/JDUNCA~1/AppData/Local/Temp/96a348bea3544f0889040dc44ad74fd2/PIC16F876A/Debug/%INFILE_NAME%.cof’ not found I’ve looked at the PBP.XML file created by Darrel Taylor but can’t see much that would affect this. Darrel must have been working with the Proteus people when he wrote this so he’d have the necessary interface info and know what was happening on the Proteus side of the interface. Sad that he’s not around to query about this; he was always very willing to help. I’ll keep puttering. Please let me know if you find a setup technique that gives consistent results…thanks. chico |
||
|
This file is a part of the Microsoft Windows system. EXE is short for executable and these types of files are used on Windows computers to install or run software.
Some programs may need pds.exe to run properly, so if this file is missing you may encounter issues when trying to launch applications or games. Often, you will get an error message that says “pds.exe missing” that tells you which specific file needs to be restored so that the application or game can continue functioning.
To resolve these issues caused by a missing pds.exe, read the suggestions below.
Author:
Intel Corporation
Process:
CBA — Ping Discovery Service
Part of:
Intel Common Base Agent
Common path(s):
subfolder %SYSTEM%
Filesize(s):
17,920 bytes, 42,744 bytes, 38,696 bytes, 18,944 bytes, 42,776 bytes, 38,648 bytes, 38,680 bytes
How to fix pds.exe missing error?
If the pds.exe missing error appears on your PC, you can use the methods below. Some are automatic, which means you can start a process to let the system automatically restore the file. Others are manual, meaning you will have to manually download pds.exe and move it to the correct program installation folder. If you are not very experienced with digging through system files and would prefer not to, you can simply go straight to an automatic method.
Here our list of solutions to try:
- Method 1: Download pds.exe
- Method 2: Fix the missing pds.exe error automatically
- Method 3: Update drivers to restore missing .exe files
- Method 4: Scan your PC for malware
- Method 5: Use System File Checker (SFC)
- Method 6: Fix corrupted pds.exe file by performing System Restore
Method 1: Download pds.exe
This is the most straightforward approach, but it is fully manual and will require you to download the right exe file and place it in the correct folder on your PC.
Look through the list of available versions of pds.exe then select the correct file and click “Download”. If you are unsure which one to download, read the section below or choose an automatic method.
How to choose the correct version of pds.exe?
When looking through the list of EXE files, pay attention to whether it’s a 64-, or 32-bit file, as well as the language it uses. For 64-bit programs, use 64-bit files if they are listed above.
It’s best to choose those EXE files whose language corresponds to the language of your program, if possible. It’s also recommended to choose the latest version to ensure up-to-date functionality.
As long as you get these two parameters right, you won’t have any issues downloading the right file.
Where to place the pds.exe file?
After you’ve downloaded the correct EXE file, place it inside the program installation folder. Alternatively, you can put the pds.exe file within the Windows system directory.
How to register pds.exe?
If placing the missing pds.exe file into the proper directory doesn’t seem to solve the problem, this means you need to register it. To do so, copy your EXE file to the C:WindowsSystem32 folder, then open a command prompt with administrator privileges. There, type “regsvr32 pds.exe” and press Enter.
Method 2: Fix the missing pds.exe error automatically
Outbyte PC Repair allows you to automatically repair EXE errors, without you having to worry about choosing the right file or registering it. The utility will not only download the correct version of pds.exe for free and suggest the right directory to install it to but will also resolve other issues related to the pds.exe file.
- Download pds.exe
- Fix the missing pds.exe error automatically
- Update drivers to restore missing .exe files
Method 3: Update drivers to restore missing .exe files
Driver updates for the Windows operating system, as well as for network adapters, monitors, printers, etc., can be downloaded individually and installed from the Windows Update Center or by using specialized utilities.
Option 1 — Automatic Device Drivers Update
Outbyte Driver Updater automatically updates drivers on Windows. Routine manual driver updates are now a thing of the past. Just with a few clicks you can automatically search your system for outdated drivers and update all of them.
- Download the Outbyte Driver Updater
- Install the application
- Launch the app
- Driver Updater will scan your system for outdated and missing drivers
- Click Update to automatically update all drivers
Option 2 — Manually Update Device Drivers
Of course, you can also choose to update your drivers yourself one by one. First you will need to look through them to find the outdated ones, then search for the updates online. Here’s how to do that:
- Go to Taskbar’s search box and type Device Manager, then select Device Manager in the search results.
- Select a category to look at the devices’ names — right-click the one that needs to be updated
- Choose Search automatically for updated driver software
- Select Update Driver
- Windows might not be able to find the new driver automatically. In this case, you can find the driver on the manufacturer’s website, where all the necessary instructions are available. Just make sure to find the official website so that you only download the trusted driver and not some malicious software.
Method 4: Scan your PC for malware to fix the pds.exe error
Since EXE files communicate directly with your system to give instructions, they are very common targets for malware, which can intentionally corrupt these files in order to substitute them with its own malicious files. If you suspect that this is what’s causing errors on your system, you should scan your computer for malware and eliminate it as soon as possible.
Option 1 — Windows Defender
The new version of Windows 10 has a built-in application called «Windows Defender», which allows you to check your computer for viruses and remove malware. In order to use the Windows Defender offline scan, follow these steps:
- Press the Win key or click Start and click on the gear icon to open Settings. Alternatively press Win + I key combination.
- Select the Update and Security option and go to the Windows Defender section.
- At the bottom of the Defender settings there is a checkbox labeled «Windows Defender Offline scan». To start it, click «Scan Now». Note that you will have to save all unsaved data before restarting your PC.
After you click the “Scan Now” button, the computer will reboot and automatically start searching for viruses and malware. Upon completion of the scan, the computer will restart, and in the notifications, you will see a report on the completed scan.
Option 2 — Outbyte AVarmor
Outbyte products are some of the most popular and effective programs for dealing with malware and unwanted programs, and they will come in handy even if you have a high-quality third-party antivirus installed. This software is specifically designed to complement your antivirus, not replace it. In the new version of Outbyte, scans can be performed in real time and manually. To initiate a manual scan please follow the steps below:
- Launch Outbyte AVarmor and click the Scan Now button. Also, you can select the Scan option on the left side of the program’s window and click Full Scan. The system will begin scanning and you will be able to see the scan results.
- Select items that you want to quarantine and press the “Quarantine Selected” button. After they’ve been quarantined, you may be prompted to reboot the computer.
- After the program has been restarted, you can delete all quarantined objects by going to the appropriate section of the program. However, if you found that your system started to encounter errors after something was quarantined, you should restore the file instead.
Check your system performance to eliminate file conflicts and junk accumulation. Resolve registry and missing file errors.
Compatible with Windows 7, 8, 10, 11
Method 5: Fix the pds.exe missing error with System File Checker (SFC)
Many users are familiar with the sfc/scannow system file integrity check command, which automatically checks and fixes protected Windows system files. It is often one of the first things experienced Windows users do when they encounter errors.
To execute this command, you have to run Command Prompt as an administrator.
- Start the command line as an administrator in Windows by pressing the Win key on your keyboard and typing «Command Prompt» in the search field, then — right-click on the result and select “Run as administrator”. Alternatively, you can press the Win + X key combination which will open the menu where you can select Command Prompt (Admin).
- Type sfc / scannow while in Command Prompt and hit Enter. After entering the command, a system check will begin. It will take a while, so please be patient. Once the process is complete you will see this message: “Windows Resource Protection found corrupt files and successfully repaired them.” or “Windows Resource Protection found corrupt files but was unable to fix some of them”.
Keep in mind that System File Checker (SFC) cannot fix integrity errors for those system files that are currently being used by the operating system. To fix these files you have to run SFC command through the command prompt in the Windows recovery environment. You can get into Windows Recovery Environment from the login screen by clicking Shutdown, then holding down the Shift key while selecting Restart.
In Windows 10, you can press Win key, select Settings > Update & security > Recovery and under Advanced Startup, click Restart now. You can also boot from the installation disk or bootable USB flash drive with the Windows 10 distribution. On the installation screen select your preferred language and then select “System Restore”. After that, go to “Troubleshooting” > “Advanced Settings” > “Command Prompt”. Once in Command Prompt type the following command: sfc /scannow /offbootdir=C: /offwindir=C:Windows, where C is the partition with the installed operating system and C:Windows, is the path to the Windows 10 folder.
This operation will take a while and it is important to wait until it is complete. When finished, close the command prompt and restart the computer as usual. You should find that the pds.exe missing error is gone.
Method 6: Fix the corrupted pds.exe file by performing a System Restore
System Restore is very useful if you want to fix pds.exe error, or almost any other error. Using the «System Restore» function, you can choose to restore Windows to a date when the pds.exe file was not damaged. Restoring Windows to an earlier date cancels changes that were made to system files since that date. Please follow the steps below to roll back Windows using System Restore and get rid of the pds.exe error.
- Press the Win + R keys combination to launch the Run dialog.
- Type sfc /scannow while in Command Prompt and hit Enter.
After entering the command, a system check will begin. It will take a while, so please be patient. Once the operation is complete you will see this message: “Windows Resource Protection found corrupt files and successfully repaired them.” or “Windows Resource Protection found corrupt files but was unable to fix some of them”.
- Type rstrui in the Run text box and click OK or hit Enter. This will open the system recovery utility.
- The “System Restore” window may include the “Choose a different restore point” option. If so, select this option and click Next. Check the “Show more restore points” checkbox to see a complete list of dates.
- Click the «Next» button and then click «Finish» to confirm your restore point. At this point, your computer will reboot normally and boot up with a restored version of Windows, and the pds.exe error should be resolved.