Thanks to all who posted hints and steps they've used to get this working.
I've reviewed all the "tricks" some have said they did to allow PEP2 to install on Win10. For example, this post: [Link: remotecentral.com]
I've spent hours these past 2 weeks with repeated installs of Win10 for the purpose of testing PEP2/PEP3 installs.
I'm happy to say that albeit I have tried all of these "tricks", some with success, there's a much simpler way to get PEP2 (PEP3 not tested but likely the same) installed to your system without having to pre-create folders or set any permissions.
In fact, I was able to run the PEP2 installer without using Administrator mode with issues.
I've successfully installed PEP2 on both 32 bit and 64 bit Windows 10 (last ISO available from Microsoft).
The process is really simple:
1. Before installing PEP, ensure that you have .NET 3.5 installed to your machine. This is done by adding a Windows Feature. See this link:
.NET 3.5 is not installed by default on Win10 as it was on Win7. It is required for PEP to operate properly.
If you don't do this prerequisite step, PEP will attempt to have Windows install the feature but the installer does not always wait for the feature to install before proceeding. It is therefore best practice to install beforehand.
2. Upon starting the PEP2/PEP3 install, open the Task Manager and go to the 'Detail' view as you will need to end the ProntoDataServer.exe process mid-way through the install.
The real cause of installer hangs! It seems that for Windows XP and Windows 7 when the PEP installer copied the ProntoDataServer.exe to your disk and installed as a service, XP and Win7 did not launch the executable immediately. This is not the case with Windows 10. As soon as the service is installed, ProntoDataServer.exe runs and causes the installer to hang at either "creating uninstall" or "creating desktop icon".
So, when the installer seems to hang, simply find the ProntoDataServer.exe process in the 'Detail' view of the Task Manager, right-click, and select 'End Task'.
Once you kill this process, the installer will complete successfully with no issues and you will see the new factory database located at: C:\ProgramData\Phillips\Common Database\componentdatabase.db
Note that you may have to select via explorer to view hidden files/directories but it is indeed there.
I have successfully backed up and restored databases, galleries, and edited codes in the database from within PEP2.
I also know that if you enable Windows Firewall setting for the Extender Discovery Tool, that works as well.
I was also able to install new firmware to my TSU9600 with no issues as well.
Things not working One thing that I've experienced is when closing the Tools Window in PEP2, an error occurs stating 'Invalid Parameter'. You can simply click on this to continue with no ill-effect.
Another item is the Web Help (F1). It does not render anything really well. However, you may find that you can browse the folder with Chrome or Firefox and maybe get more information. One thing I will note is that besides the fact that the older help neglects My Database, I personally like the PEP1 Help file or even the original ProntoEdit or ProntoEditProNG help files. I find that having a read through these or the Classic Pronto FAQ on this site really prepares you for the leap that was taken for PEP2 and continued into PEP3.
If you are reading this, I'd love to hear about your results as this will allow me to breathe extra life into my Prontos and carry forward for sure on Win10 and likely Win11 (Not tested).
Lyndel
Last edited by Lyndel McGee on June 30, 2023 22:53.
