- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Error -5001 while launching InstallScript Setup
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hello Team,
the error occurs directly after launching the setup, right before the splashscreen should appear.
Please notice the attachments: Screenshots of the error message and the system information.
The content of the error message text field is:
Error Code: -5001 : 0xffffec75
Error Information:
>setup.cpp (243)
PAPP:
PVENDOR:
PGUID:
$27.0.122
@Windows 10 / Server 2016 Service Pack 0 (19044)
IE Version: 9.11.19041.0
I'd appreciate it if someone has a solution
Best regards
Ralf
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi, it looks like a runtime error for the C++ environment which InstallShield is using, so installing the latest VC Runtime could help. On the other hand I don't know if there are restrictions for the Internet of Things (IOT) edition of Windows 10, maybe sfc /scannow could also fix it.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi, thanks for the suggestions. They seem helpful to me. In this case, however, the problem was suddenly solved after the PC was connected to a different network port. Unfortunately, I hadn't mentioned in the error description that there were also problems with network access before the error message occured.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi, it looks like a runtime error for the C++ environment which InstallShield is using, so installing the latest VC Runtime could help. On the other hand I don't know if there are restrictions for the Internet of Things (IOT) edition of Windows 10, maybe sfc /scannow could also fix it.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Hi, thanks for the suggestions. They seem helpful to me. In this case, however, the problem was suddenly solved after the PC was connected to a different network port. Unfortunately, I hadn't mentioned in the error description that there were also problems with network access before the error message occured.