the Using Homegate with Windows 11

Hi All
I tried to load Homegate onto a new windows 11 machine and windows took exception to the dongle, it took exception to software loaded for the dongle, Is there a known answer for this?
Thanks in advance
Mike

 

ditch home gate and use schedule plus - the last versions do not require a dongle and the fact you have one means you have purchased it basically.

 

Thanks for this advice, I'm back up and running with schedule plus and C-Gate 3, I've downloaded Piced 4.15.2
Am I safe using Piced and C-Gate 3 to update my C-Touch Colour and my PAC?

Thanks in advance
Mike
P.S. I still can't see why Clipsal can't make my HomeGate USB Dongle work with Windows 11 :-(

 

It is probably the reason why they ditched the dongles all together - as they are 3rd party devices so you have no control over the hardware and software updates. I think the dongles have been sort of been obsolete for 5 or 6 years. if you are changing anything in the Ctouch piced will make you do a firmware update - the only thing depending on where you are updating from Version wise is the ability to to do some stuff if connect to Dali control as only line A would work, I cannot recall any other issues I encountered, but if you are not changing anything on them there is really no harm in just letting them do what they are doing.

 

I say ditch the lot and go an AC2 .. saves leaving a PC on 24x7 with all the security updates and patches, etc and is a lot easier to keep updated than a PAC (you dont need to serial/USB to it!) ..

You can keep the CTouch as a touch screen, use the AC2 from your phone, etc and replace the CTouch with an ipad or similar when it dies.

 

Why spend 2k on AC2 if your whole setup is running of piced style program. A low powered PC draws sweet FA, all your programming is already in pascal and done within the same program environment. An isolated PC is easy to keep secure and you don't need to drop a heap of time redoing visualisations and moving coding to Lua?

 

Yes I tried it but all versions are the same.
It's the software it loads for the dongle that's the problem, if you have done a clean instal of windows 11 and the try and install any Homegate the at least win 11 warns you that the dongle isn't compatible!!

I'm not trying again until someone tells me Homegate ver xxxx has fixed the problem!

 

Update Last week Having removed the dongle from my Cbus machine, I updated from windows 10 to Windows 11
of course because I upgraded and kept my files ..
It place the dongle software back into my new windows 11 directory ;-( ;-(

The file causing all the hassle is SNTUSB64.sys
I hate it!! I've deleted one of the two so far!!!

If Cbus can't fix this they should send us a de-dongled version of Homegate!!!

 

Hi Colin
Below are both PC I'm using with windows 11
Both had the SNTUSB64.sys problem.
Hope this helps you
Mike

Device name MGU-Ty
Processor 12th Gen Intel(R) Core(TM) i5-12400 2.50 GHz
Installed RAM 16.0 GB (15.7 GB usable)
Device ID 91DA083E-30C1-49F6-BF25-1B664E7BEBDD
Product ID 00330-80015-37670-AA171
System type 64-bit operating system, x64-based processor
Pen and touch Pen and touch support with 10 touch points
Edition Windows 11 Pro
Version 24H2
Installed on ‎11/‎05/‎2025
OS build 26100.4202
Experience Windows Feature Experience Pack 1000.26100.107.0

Device name Study-4K
Processor 12th Gen Intel(R) Core(TM) i7-12700K 3.60 GHz
Installed RAM 32.0 GB (31.7 GB usable)
Device ID F4533414-8103-492E-AFD1-8E9134D248A4
Product ID 00330-52868-83360-AAOEM
System type 64-bit operating system, x64-based processor
Pen and touch No pen or touch input is available for this display
Edition Windows 11 Pro
Version 24H2
Installed on ‎13/‎02/‎2025
OS build 26100.4202
Experience Windows Feature Experience Pack 1000.26100.107.0

 

MGU-Ty was running Homegate under Windows 10
Study-4k is new and has never run windows 10

I still have a copy of SNTUSB64 .sys located in :
C:\Windows\System32\DriverStore\FileRepository\sntusb64.inf_amd64_1a428f854ef9139a\SNTUSB64.SYS
on the MGU-ty Machine which I cant get rid of so I cant enable Memory integrity!! see attached jpg




here is the content sntusb64.inf file:
; SafeNet Sentinel SuperPro/UltraPro/HardwareKey USB driver INF file
;
; Copyright (C) 2009 SafeNet, Inc., All rights reserved.
[Version]
Signature="$CHICAGO$"
Class=USB
ClassGuid={36fc9e60-c465-11cf-8056-444553540000}
CatalogFile=sntusb64.cat
provider=%SafeNet%
DriverVer=08/06/2009, 7.5.1.0
[Manufacturer]
%SafeNet%=SafeNet,NTamd64
[SafeNet.NTamd64]
%USB\VID_04B9&PID_0300.DeviceDesc%=SNTUSB64, USB\VID_04B9&PID_0300
%USB\VID_04B9&PID_0301.DeviceDesc%=SNTUSB64, USB\VID_04B9&PID_0301
%USB\VID_04B9&PID_0302.DeviceDesc%=SNTUSB64, USB\VID_04B9&PID_0302
%USB\VID_04B9&PID_0303.DeviceDesc%=SNTUSB64, USB\VID_04B9&PID_0303
%USB\VID_04B9&PID_0304.DeviceDesc%=SNTUSB64, USB\VID_04B9&PID_0304
%USB\VID_04B9&PID_8000.DeviceDesc%=SNTUSB64, USB\VID_04B9&PID_8000
%USB\VID_04B9&PID_8001.DeviceDesc%=SNTUSB64, USB\VID_04B9&PID_8001
%USB\VID_04B9&PID_8002.DeviceDesc%=SNTUSB64, USB\VID_04B9&PID_8002
%USB\VID_04B9&PID_8003.DeviceDesc%=SNTUSB64, USB\VID_04B9&PID_8003
%USB\VID_04B9&PID_8004.DeviceDesc%=SNTUSB64, USB\VID_04B9&PID_8004
%USB\VID_04B9&PID_8005.DeviceDesc%=SNTUSB64, USB\VID_04B9&PID_8005
[SourceDisksNames]
1=%DiskName%,,,
[SourceDisksFiles]
SNTUSB64.SYS=1,,
[ControlFlags]
; All PnP devices should be excluded from manual AddDevice Applet list
ExcludeFromSelect = USB\VID_04B9&PID_0300
[DestinationDirs]
DefaultDestDir = 12
SNTUSB64.SysCopy = 10,System32\Drivers
[SNTUSB64.NTAMD64]
CopyFiles=SNTUSB64.SysCopy
[SNTUSB64.SysCopy]
SNTUSB64.SYS
[SNTUSB64.NTAMD64.Services]
Addservice = SNTUSB64, 0x00000002, SNTUSB64.AddService
[SNTUSB64.AddService]
DisplayName = %SNTUSB64.SvcDesc%
ServiceType = 1 ; SERVICE_KERNEL_DRIVER
StartType = 3 ; SERVICE_DEMAND_START
ErrorControl = 1 ; SERVICE_ERROR_NORMAL
ServiceBinary = %12%\SNTUSB64.SYS
AddReg = SNTNLUSB.AddReg.NTAMD64
LoadOrderGroup = Base
[SNTNLUSB.AddReg.NTAMD64]
HKR,"Setup","UsbSupport",0x10001,1
HKR,"Current","VersionString",,"SSD7.5.1"
[Strings]
SafeNet="SafeNet, Inc."
DisplayClassName="Software Security Token"
USB\VID_04B9&PID_0300.DeviceDesc="SafeNet USB SuperPro/UltraPro"
USB\VID_04B9&PID_0301.DeviceDesc="SafeNet USB Security Security Token"
USB\VID_04B9&PID_0302.DeviceDesc="SafeNet USB Security Security Token"
USB\VID_04B9&PID_0303.DeviceDesc="SafeNet USB Security Security Token"
USB\VID_04B9&PID_0304.DeviceDesc="SafeNet USB Security Security Token"
USB\VID_04B9&PID_8000.DeviceDesc="SafeNet Sentinel Hardware Key"
USB\VID_04B9&PID_8001.DeviceDesc="SafeNet Sentinel Hardware Key RTC"
USB\VID_04B9&PID_8002.DeviceDesc="SafeNet Sentinel Hardware Key Mega-Memory"
USB\VID_04B9&PID_8003.DeviceDesc="SafeNet Sentinel Hardware Key Mega-Memory RTC"
USB\VID_04B9&PID_8004.DeviceDesc="SafeNet Sentinel Dual Hardware Key"
USB\VID_04B9&PID_8005.DeviceDesc="SafeNet Sentinel Dual Hardware Key RTC"
SNTUSB64.SvcDesc="SafeNet USB SuperPro/UltraPro/HardwareKey"
DiskName="Sentinel System Driver Installation Disk"