-
×InformationFix Windows 10 Update Issues
Resolve Windows 10 related issues for your HP computers or printers by HP Windows 10 Support Center
-
-
×InformationFix Windows 10 Update Issues
Resolve Windows 10 related issues for your HP computers or printers by HP Windows 10 Support Center
-
- HP Community
- >
- Apps & Services
- >
- ZCentral
- >
- RGS Reciever 7.7 wont start Win10 1909
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page

Create an account on the HP Community to personalize your profile and ask a question

RGS Reciever 7.7 wont start Win10 1909
03-17-2020 12:53 PM

Hello,
i have a Windows 10 computer with Windows Enterprise Evaluation and the current updates.
My problem is, that RGS 7.7 closes itsselfs directly after the splashscreen.
I cranked up the logging to debug, but the log stays empty.
I also installed the latest vcredis pakages in x64 and x84 architecture.
Other Machines with the same windows version do run well.
The problem persists after reinstalling the Software.
I also tryed the 7.5 and 7.65 versions.
03-20-2020 08:39 PM

Check to see if the directory %HOMEPATH%/hpremote exists and write permissions are enable for the user.
Is there a Windows Application event log entry for the receiver?
I work on behalf of HP.
03-24-2020 08:04 AM

We encountered the same issue. Reinstalling, vcredis packages, NVIDIA driver updates etc...
The real culprit was that the user on the machine had a "ç" in his username and home folder. So RGS receiver died because it wasn't able to read "c:\users\François\hpremote" . So this issue could probably affect a lot on non-english users.
03-27-2020 07:14 AM

Hi Pixel1,
If you think the root cause could be the character issue described by Jasminl, please check your PMs.
I've just messaged you a link for a 7.7 fix for that.
Thanks.
I work on behalf of HP.
04-13-2020 03:10 AM

Hello Becky,
the %HOMEPATH%/hpremote exists and has the right permissions.
The HP-Remote-Viewer does not log antything even when i set the log level to debug in the configurator.
Same for the Windows Application event log... there are only log entrys for the installation.
Anyway i think the problem could caused by an umlaut just as Jasminl sayd, because my profile name got an "ü" inside of it.
But it could be usefull to provide better debug-logging in the future.
04-13-2020 08:23 AM

Hi Pixel2,
If you believe the issue is due to an accented character on your username, please check your inbox.
I've sent a message with instructions to download an RGS fix for non-ASCII characters on your %HOMEPATH%
I work on behalf of HP.

Didn't find what you were looking for? Ask the community