EseeCloud CameraManagementSystem (CMS) Software for Hiseeu NVR

[Chuck101]

EseeCloud works perfectly on my old win 10 HP15 laptop.  I upgraded to a HP17 win 11 Pro laptop and using the same exact settings I am unable to see live video feed from the Hiseeu NVR (model K8510-w gateway software V3.6.2.11) security camera system.  I have 7 cameras which work perfectly on the old HP win 10 laptop but for some unknown reason EseeCloud on win 11 pro chokes and will not display live video.  I have taken the usual steps to no effect.  I have contacted EseeCloud and they tell me that since they have few people are using the PC software they no longer provide updates/drivers/patches.  They suggested that I continue to use the system on my old HP laptop which is 15 years old.  Are you kidding??? What happens to new Hiseeu customers; well that is not my problem.

I believe the issue is somehow hardware/driver related.  VLC streams w/o any trouble, I can watch live TV, or crap adds on websites, but I cannot view live video feed from the NVR?  Why?  What is win 10 doing that win 11 can't/won't.  What did Microsoft break this time?

Here is the rub.  I can download unseen live video and audio from a camera and play it back using VLC.  How nuts is that?

I just downloaded the latest update for my video driver from you guys and gave it a shot.  No luck.

My best guess is that something is either lost in translation from the NVR to the laptop or win 11 refuses to allow the live video in.  The firewall is configured for EseeCloud.  Perhaps an update to the NVR firmware is in order??? Hiseeu sent me a website that will display the live video feeds and it would be okay if they would put a download button in the webpage.  The browser works but NOT their software, really?

I considered using an android emulator and run the mobile version of EseeCloud that way; but it appears to be way more work than a straight up patch.  I really don't want to brick my new HP, so no.

Like the old blue screen of death this is all I get.

Any ideas?? Any patches?? Help, I'll be more than happy to beta test a patch!!!I'

Thanks and I hope you can figure it out.

This is the Hiseeu website...not that great and you are stuck with whatever they give you.

[RedCapsicum9]

...since you say that EseeCloud works flawlessly on your Windows 10 laptop, one of the first things I'd suggest is trying to run the software in compatibility mode on your new Windows 11 system. To do this, simply right-click the EseeCloud shortcut, select Properties, then head over to the Compatibility tab. From there, enable the option “Run this program in compatibility mode for:” and choose Windows 10 from the dropdown. Also, check the box for “Run this program as an administrator.” Once you apply the changes and click OK, go ahead and relaunch the app this often clears up behavior issues when older software is run on newer platforms. On top of that, make sure all your system-level drivers, particularly for the network adapter, chipset, and wireless/LAN, are fully up to date. Even if your graphics driver is current, having outdated supporting drivers can still create strange issues. You can find the latest drivers by visiting the support page for your HP17 model on HP’s official website.

It’s also worth checking your graphics settings more closely. Open your Graphics Control Panel (whether Intel or another vendor) and confirm that no hardware acceleration or power-saving settings are interfering with the video stream. You can also go to Windows Settings > System > Display > Graphics, find the EseeCloud app, and experiment with turning hardware acceleration off just for this application.

Let’s not forget about firewall permissions, double-check that EseeCloud is allowed through both private and public networks in Windows Defender Firewall. Sometimes it can be permitted on one type of network but not the other, which could explain the inconsistent behavior. To add, older applications like EseeCloud may depend on legacy components that aren’t enabled by default in Windows 11. You’ll want to open Control Panel > Programs > Turn Windows features on or off, and ensure that .NET Framework 3.5, Media Features, and DirectPlay are enabled. These often play a big role in getting vintage apps to behave on modern operating systems. Since VLC works fine with the NVR, an alternative workaround you might consider is setting up a VLC playlist using RTSP streams directly from each camera. This isn’t a long-term solution, but it can be handy while we troubleshoot the core issue with EseeCloud.

You also raised a valid point regarding the firmware, if your NVR has any available updates, installing the latest firmware could improve its ability to communicate smoothly with newer Windows environments.

Lastly, it may help to open the Event Viewer (navigate to Windows Logs > Application or System) and check for any recurring errors or warnings related to EseeCloud. These logs might offer us a behind-the-scenes look at what’s causing the failure, whether it’s an OS-level restriction, a compatibility issue, or something else entirely.

[Chuck101]

Howdy, 

I had considered a codecs problem early on and tried to install that software.  It did not work, see attachment.  And you are right I do not want to brick my brand new laptop so I'll stay away from emulators.

In the meantime I'll keep banging my head on a wall.

This is what Hiseeu sent recently:

sorry, we don't have other version to compatible with your win 11 pro.

---

Hiseeu Security Camera System Corporation

We endeavor to assist our customer with best service.

Hiseeu Abby

Facebook: Hiseeu Security Camera

From: Charles Romaine

Date: 2025-08-05 00:25

Subject: EseeCloud Not Working Windows 11 Pro

Howdy,

I am still trying to make EseeCloud work with win 11 pro and so far NOTHING has worked.

The event viewer indicates a possible problem with ntdll.dll.  What does this file do?  Is there an update for this file or another version??  Please note: I have tried ALL available versions of EseeCloud none of which work.

Anything you do to help me run your software on my win 11 pro laptop would be beneficial.

Thank you,

Charles Romaine

Source
EseeCloud.exe

Summary
Stopped working

Date
‎7/‎27/‎2025 9:25 PM

Status
Report sent

Description
Faulting Application Path:    C:\Program Files (x86)\EseeCloud\EseeCloud.exe

Problem signature
Problem Event Name:    APPCRASH
Application Name:    EseeCloud.exe
Application Version:    3.0.7.10
Application Timestamp:    62134232
Fault Module Name:    ntdll.dll
Fault Module Version:    10.0.26100.4768
Fault Module Timestamp:    97c731d0
Exception Code:    c0000005
Exception Offset:    0004fde2
OS Version:    10.0.26100.2.0.0.256.48
Locale ID:    1033
Additional Information 1:    2beb
Additional Information 2:    2beba6fb4680d73a8c78ca7c24ccdb46
Additional Information 3:    4cbe
Additional Information 4:    4cbe99a0ac1357f5f266328844d018e6

Extra information about the problem
Bucket ID:    70ee0f05148c3d48e385027f6e6c6f6f (1406533204959850351)

Thanks for trying but keep pitching and I'll keep swinging.  The solution is out there...cue x-files theme....

Chuck Romaine

Maybe the good folks at Intel can pull out a solution.

[CaNeBuRy23]

Yo what’s good my guy so check this, EseeCloud been doin’ its thing just fine on old-ass Windows 10 machines, no cap. But the moment you run that same setup on a fresh Windows 11 Pro laptop? Boom live video feed just ghosts you. Same NVR, same settings, same 7 cameras, but EseeCloud don’t wanna play nice. It opens up like it’s ready to go, but the live view? Nah, that part straight up taps out. Now you got a few moves you can make: first up, try that compatibility mode trick, shoutout to @RedCapsicum9 for droppin’ that. Or you can just skip all the nonsense and hit up the web interface, run it through an Android emulator, or go full send and start messin’ with open-source NVR clients. Now if you thinkin’ of messin’ with firmware, chill. Unless the update specifically says it's for Win11 or fixin’ stream bugs, don’t risk bricking your gear unless you got a full backup in your pocket.

Me personally, I ran into this same headache. The only thing I really checked was if Win11 had the right media codecs. And that’s a real thing Windows 11 (especially them “N” versions) be missin’ stuff like HEVC/H.265 or MPEG codecs, which your cameras need to show video. So if you ain’t done it yet, go grab that HEVC Video Extension from the Microsoft Store, get the one that says "from Device Manufacturer" 'cause it's free and it does the job. Here’s the link to the free HEVC Codec – Device Manufacturer version

Hope that helps, fam. If EseeCloud don’t step up, we just gotta out-hustle it.

[Chuck101]

I think I hit the wrong reply button for AlphaTop89, but I did reply.

I think I'll try the infamous, refresh....

Thanks for trying but keep pitching and I'll keep swinging.

Chuck Romaine

[Chuck101]

Refresh, what a waste of time.  It is incredible that everything works great but for EseeCloud.

I'll keep trying.

[Chuck101]

It would seem that Intel has closed this problem out and I am left to fend for myself.  Thanks to all who have tried to help.

[Chuck101]

Howdy,

I keep checking from time to time to see if there is a solution.  I thought there was one named, gfx_win_101.8136.exe,  that was mentioned elsewhere, but it did not work and it exited with ERROR 8, no found file for this device:

(EXIT CODE 😎

2025/10/18 13:05:25.413|INFO|Logging started on 2025/10/18 13:05:25.408 ||
2025/10/18 13:05:25.413|INFO|Scanning for hardware changes ||
2025/10/18 13:05:25.793|INFO|Installer version: 1.0.1084.3 ||
2025/10/18 13:05:25.793|INFO|Installer initial executable path: "C:\Users\charl\AppData\Local\Temp\RarSFX0\Installer.exe" ||
2025/10/18 13:05:25.793|INFO|Installer main executable path: "C:\Users\charl\AppData\Local\Temp\Intel\Installer\Installer.exe" ||
2025/10/18 13:05:25.793|INFO|Installer parent process module path: "C:\Users\charl\AppData\Local\Temp\RarSFX0\Installer.exe" ||
2025/10/18 13:05:25.793|INFO|Installer startup type: WindowsPowerShell ||
2025/10/18 13:05:25.793|INFO|Installer root directory: "C:\Users\charl\AppData\Local\Temp\Intel\Installer\" ||
2025/10/18 13:05:25.793|INFO|Command line arguments: C:\Users\charl\Downloads\gfx_win_101.8136.exe ||
2025/10/18 13:05:25.793|INFO|Language of the user interface: [en-US] ||
2025/10/18 13:05:25.793|INFO|Operating system specification: Microsoft Windows NT 10.0.26100.0 ||
2025/10/18 13:05:25.793|INFO|Operating system boot time: 2025-10-18 12:19:30 ||
2025/10/18 13:05:25.793|INFO|Operating system boot mode: Normal ||
2025/10/18 13:05:26.011|INFO|CPU base clock: 1200Mhz ||
2025/10/18 13:05:26.011|INFO|Test Signing: OFF ||
2025/10/18 13:05:26.011|INFO|Windows Media Player status: Installed ||
2025/10/18 13:05:26.011|INFO|Non-Interactive mode flag: False ||
2025/10/18 13:05:26.107|INFO|Bitlocker protection status: PROTECTION_ON ||
2025/10/18 13:05:26.107|INFO|Smart App Control status: SACStatus_Enabled ||
2025/10/18 13:05:26.107|INFO|Setting admin access rights - Directory: C:\Users\charl\AppData\Local\Temp\Intel\Installer\. ||
2025/10/18 13:05:26.107|INFO|Setting admin access rights - DONE ||
2025/10/18 13:05:26.386|INFO|
INF files in installer location:
{
"C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\DisplayAudio\12.1\IntcDAud.inf",
"C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\MSHdaDac.inf",
"C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\iigd_dch.inf",
"C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\HdBusExt.inf",
"C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\CtaChildDriver\CtaChildDriver.inf",
"C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\GSCAuxDriver.inf",
"C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\gscheci.inf",
"C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\memcntrl.inf",
"C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\I2CDriver\Intel_NF_I2C_Child.inf",
"C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\iigd_dch_d.inf",
"C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\PmtChildDriver\PmtChildDriver.inf",
}
||
2025/10/18 13:05:26.819|INFO|Gen12+ platform: False ||
2025/10/18 13:05:26.819|INFO|Dynamic background: False ||
2025/10/18 13:05:26.821|INFO|"Installer" process priority class: High ||
2025/10/18 13:05:28.157|INFO|Creating event object with name "Global\IntelGfxInstallerUIRendered"... ||
2025/10/18 13:05:28.157|INFO|Creating event object with name "Global\IntelGfxInstallerUIRendered" - DONE ||
2025/10/18 13:05:28.166|INFO|Received signal from "Global\IntelGfxInstallerUIRendered" ||
2025/10/18 13:05:28.456|INFO|
Supported INF files in DriverStore:
{
{
Driver Store location: "C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_fe38470d802dc9be\iigd_dch.inf"
Published name: "oem14.inf"
}
{
Driver Store location: "C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_189ed46b2c5eef09\iigd_dch.inf"
Published name: "oem133.inf"
}
{
Driver Store location: "C:\Windows\System32\DriverStore\FileRepository\cui_dch.inf_amd64_f59546749400c6b2\cui_dch.inf"
Published name: "oem10.inf"
}
{
Driver Store location: "C:\Windows\System32\DriverStore\FileRepository\cui_dch.inf_amd64_7c2c42e9f26e801b\cui_dch.inf"
Published name: "oem199.inf"
}
{
Driver Store location: "C:\Windows\System32\DriverStore\FileRepository\iigd_ext.inf_amd64_9f2777d19b4d146a\iigd_ext.inf"
Published name: "oem82.inf"
}
{
Driver Store location: "C:\Windows\System32\DriverStore\FileRepository\cui_dch.inf_amd64_4f43a1c1898e6696\cui_dch.inf"
Published name: "oem130.inf"
}
{
Driver Store location: "C:\Windows\System32\DriverStore\FileRepository\intcdaud.inf_amd64_1036173dcec6146d\intcdaud.inf"
Published name: "oem131.inf"
}
{
Driver Store location: "C:\Windows\System32\DriverStore\FileRepository\hdbusext.inf_amd64_8d10e5d67ac6f211\hdbusext.inf"
Published name: "oem95.inf"
}
{
Driver Store location: "C:\Windows\System32\DriverStore\FileRepository\mshdadac.inf_amd64_a3dba0ec23114215\mshdadac.inf"
Published name: "oem31.inf"
}
{
Driver Store location: "C:\Windows\System32\DriverStore\FileRepository\igcc_dch.inf_amd64_4b6e72c945d3dca7\igcc_dch.inf"
Published name: "oem27.inf"
}
}
||
2025/10/18 13:05:28.696|WARN|Could not find INF for extension driver in Driver Store. Device: Intel® Smart Sound Technology OED, Published OEM INF: oem92.inf ||
2025/10/18 13:05:28.696|WARN|Could not find INF for extension driver in Driver Store. Device: Intel® Smart Sound Technology OED, Published OEM INF: oem217.inf ||
2025/10/18 13:05:28.801|WARN|Cannot find compatible drivers for device with device instance id "SWD\DRIVERENUM\{002C4697-5B34-4222-B9C9-6277B0869281}#IPFEFEXTCOMPONENT&4&24591892&0". The device does not exist. ||
2025/10/18 13:05:29.770|WARN|Could not find INF for extension driver in Driver Store. Device: Intel(R) Innovation Platform Framework Processor Participant, Published OEM INF: oem146.inf ||
2025/10/18 13:05:29.770|WARN|Could not find INF for extension driver in Driver Store. Device: Intel(R) Innovation Platform Framework Processor Participant, Published OEM INF: oem210.inf ||
2025/10/18 13:05:29.996|WARN|Could not find INF for extension driver in Driver Store. Device: Intel(R) PCI Express Root Port #10 - 51B1, Published OEM INF: oem211.inf ||
2025/10/18 13:05:30.419|WARN|Could not find INF for extension driver in Driver Store. Device: Intel® Smart Sound Technology for Digital Microphones, Published OEM INF: oem289.inf ||
2025/10/18 13:05:30.419|WARN|Could not find INF for extension driver in Driver Store. Device: Intel® Smart Sound Technology for Digital Microphones, Published OEM INF: oem261.inf ||
2025/10/18 13:05:30.419|WARN|Could not find INF for extension driver in Driver Store. Device: Intel® Smart Sound Technology for Digital Microphones, Published OEM INF: oem298.inf ||
2025/10/18 13:05:31.442|WARN|Could not find INF for extension driver in Driver Store. Device: Intel(R) PCI Express Root Port #5 - 51BC, Published OEM INF: oem211.inf ||
2025/10/18 13:05:31.956|WARN|Could not find INF for extension driver in Driver Store. Device: Intel(R) LPC Controller - 5182, Published OEM INF: oem211.inf ||
2025/10/18 13:05:32.417|INFO|

Intel devices with matching INF files:
{
{
Device
{
Device name: Intel(R) Serial IO I2C Host Controller - 51E8
Device instance path: PCI\VEN_8086&DEV_51E8&SUBSYS_899B103C&REV_01\3&11583659&1&A8
Device manufacturer: Intel Corporation
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_adl.inf_amd64_563fbcd35feb69a6\ialpss2_i2c_adl.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel® Smart Sound Technology OED
Device instance path: INTELAUDIO\DSP_CTLR_DEV_51C8&VEN_8086&DEV_0222&SUBSYS_8D56103C&REV_0001\4&1EC06B17&0&0800DIF_000A&UIF_0000
Device manufacturer: Intel(R) Corporation
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\intcoed.inf_amd64_e8618fcf8584a7f6\intcoed.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) Innovation Platform Framework Extensible Framework
Device instance path: SWD\DRIVERENUM\{002C4697-5B34-4222-B9C9-6277B0869281}#IPFEFEXTCOMPONENT&4&24591892&0
Device manufacturer: Intel
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_a50addc1f126c381\ipf_cpu.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) Innovation Platform Framework Extensible Framework
Device instance path: SWD\DRIVERENUM\IPFEFEXTCOMPONENT&4&24591892&0
Device manufacturer: Intel
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_a50addc1f126c381\ipf_cpu.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) UHD Graphics
Device instance path: PCI\VEN_8086&DEV_46B3&SUBSYS_899B103C&REV_0C\3&11583659&1&10
Device manufacturer: Intel Corporation
}
All matching/supported Driver Store INF files:
{
INF file path: "C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_fe38470d802dc9be\iigd_dch.inf"
INF file date: "07/08/2024"
INF file version: "32.0.101.5763"
INF Models Section: "IntelGfx.NTamd64.10.0...25952"
INF Models Entry: "Intel(R) UHD Graphics = iADLPD_w10_DS,PCI\VEN_8086&DEV_46B3&SUBSYS_899B103C"
}
{
INF file path: "C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_189ed46b2c5eef09\iigd_dch.inf"
INF file date: "07/29/2025"
INF file version: "32.0.101.6987"
INF Models Section: "IntelGfx.NTamd64.10.0...25952"
INF Models Entry: "Intel(R) UHD Graphics = iADLPD_w11_DS,PCI\VEN_8086&DEV_46B3"
}
INF file in use by device:
{
INF file path: "C:\Windows\System32\DriverStore\FileRepository\iigd_dch.inf_amd64_fe38470d802dc9be\iigd_dch.inf"
INF file date: "07/08/2024"
INF file version: "32.0.101.5763"
INF Models Section: "IntelGfx.NTamd64.10.0...25952"
INF Models Entry: "Intel(R) UHD Graphics = iADLPD_w10_DS,PCI\VEN_8086&DEV_46B3&SUBSYS_899B103C"
}
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) SMBus - 51A3
Device instance path: PCI\VEN_8086&DEV_51A3&SUBSYS_00000000&REV_01\3&11583659&1&FC
Device manufacturer: INTEL
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\alderlakepch-psystem.inf_amd64_c27bc8858e991c72\alderlakepch-psystem.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) Management Engine Interface #1
Device instance path: PCI\VEN_8086&DEV_51E0&SUBSYS_899B103C&REV_01\3&11583659&1&B0
Device manufacturer: Intel
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\heci.inf_amd64_aed09f4a041aa7ed\heci.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) Serial IO GPIO Host Controller - INTC1055
Device instance path: ACPI\INTC1055\2&DABA3FF&1
Device manufacturer: Intel Corporation
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_gpio2_adl.inf_amd64_6f8ae740d22247ce\ialpss2_gpio2_adl.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) iCLS Client
Device instance path: SWD\DRIVERENUM\OEM_ES_COMPONENT&4&1F48F8BF&0
Device manufacturer: Intel
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\iclsclient.inf_amd64_740dc8aba9846dbb\iclsclient.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) Dynamic Tuning Technology Device Extension Component
Device instance path: SWD\DRIVERENUM\{BC7814A1-A80E-44B3-87C6-652EAC676387}#DTTEXTCOMPONENT&4&24591892&0
Device manufacturer: Intel
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\dtt_sw.inf_amd64_683097297aaa9bb4\dtt_sw.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) Innovation Platform Framework Processor Participant
Device instance path: PCI\VEN_8086&DEV_461D&SUBSYS_899B103C&REV_04\3&11583659&1&20
Device manufacturer: Intel
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_cpu.inf_amd64_a50addc1f126c381\ipf_cpu.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Realtek OVWrapN Component
Device instance path: SWD\DRIVERENUM\{C3A63EDD-2D27-4B66-B155-5E94B43D926A}#REALTEKOVWRAPN&6&26300440&0
Device manufacturer: Realtek
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\ovwrapn.inf_amd64_8d63ad46e9611e59\ovwrapn.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) PCI Express Root Port #10 - 51B1
Device instance path: PCI\VEN_8086&DEV_51B1&SUBSYS_899B103C&REV_01\3&11583659&1&E8
Device manufacturer: INTEL
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\alderlakepch-psystem.inf_amd64_c27bc8858e991c72\alderlakepch-psystem.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel® Smart Sound Technology Detection Verification
Device instance path: INTELAUDIO\DIF_0000&UIF_0000&CTLR_DEV_51C8&VEN_8086&DETECTIONVERIFICATION\5&161EAF8F&0&DIF_000A&UIF_0000
Device manufacturer: Intel(R) Corporation
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\detectionverificationdrv.inf_amd64_2450e0c5ef2ed9a7\detectionverificationdrv.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel® Smart Sound Technology BUS
Device instance path: PCI\VEN_8086&DEV_51C8&SUBSYS_8D56103C&REV_01\3&11583659&1&FB
Device manufacturer: Intel(R) Corporation
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\intcaudiobus.inf_amd64_18b59ee708f416b3\intcaudiobus.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Synaptics Service binaries
Device instance path: SWD\DRIVERENUM\SYNSERVICE&6&22FEDE9F&1
Device manufacturer: Synaptics
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\synservice.inf_amd64_01c407f5ab896090\synservice.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel® Smart Sound Technology for Digital Microphones
Device instance path: INTELAUDIO\CTLR_DEV_51C8&LINKTYPE_02&DEVTYPE_00&VEN_8086&DEV_AE20&SUBSYS_8D56103C&REV_10EC\5&161EAF8F&0&0000DIF_000A&UIF_0000
Device manufacturer: Intel(R) Corporation
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\intcdmic.inf_amd64_4dba41d4af60eaad\intcdmic.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: HP Application Enabling Services
Device instance path: SWD\DRIVERENUM\{30E20916-51CC-469C-AD2D-EAEEE7624B3B}#FUSIONSOFTWARE.10.0...16299&4&23669C0E&0
Device manufacturer: HP
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\hpcustomcapcomp.inf_amd64_b1bfb66eda7ba5ab\hpcustomcapcomp.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: DTS APO4x Service Component
Device instance path: SWD\DRIVERENUM\{B410CF85-2754-43A3-8963-A5D32D640E22}#DTSSERVICE&6&26300440&0
Device manufacturer: DTS
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\dtsapo4xservice.inf_amd64_5d9c39fe4d89dcaf\dtsapo4xservice.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) Innovation Platform Framework Base Provider
Device instance path: SWD\DRIVERENUM\{002C4697-5B34-4222-B9C9-6277B0869281}#IPFBASEPROVIDERCOMPONENT&4&24591892&0
Device manufacturer: Microsoft
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\c_swcomponent.inf_amd64_1536c854ab7bdc83\c_swcomponent.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) Management Engine WMI Provider
Device instance path: SWD\DRIVERENUM\OEM_WMI_COMPONENT&4&1F48F8BF&0
Device manufacturer: Intel
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\mewmiprov.inf_amd64_58a0ea2de06916f7\mewmiprov.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: HP Device Health Service
Device instance path: SWD\DRIVERENUM\{DBF3223D-8A64-4DAE-903E-E2FAD8D45BC8}#HPANALYTICSSOFTWARE.10.0...16299&4&23669C0E&0
Device manufacturer: HP
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\hpanalyticscomp.inf_amd64_0f2b4c962c16d743\hpanalyticscomp.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) Shared SRAM - 51EF
Device instance path: PCI\VEN_8086&DEV_51EF&SUBSYS_00000000&REV_01\3&11583659&1&A2
Device manufacturer: INTEL
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\alderlakepch-psystem.inf_amd64_c27bc8858e991c72\alderlakepch-psystem.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) Dynamic Application Loader Host Interface
Device instance path: SWD\DRIVERENUM\OEM_DAL_COMPONENT&4&1F48F8BF&0
Device manufacturer: Intel
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\dal.inf_amd64_8a3f88e34f6b8385\dal.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) GNA Scoring Accelerator module
Device instance path: PCI\VEN_8086&DEV_464F&SUBSYS_899B103C&REV_04\3&11583659&1&40
Device manufacturer: Intel Corporation
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\gna.inf_amd64_8e2f374849f1eba9\gna.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Realtek OVWrap2 Component
Device instance path: SWD\DRIVERENUM\{C3A63EDD-2D27-4B66-B155-5E94B43D926A}#REALTEKOVWRAP2&6&26300440&0
Device manufacturer: Realtek
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\ovwrap2.inf_amd64_b9853483bbac070b\ovwrap2.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) PCI Express Root Port #5 - 51BC
Device instance path: PCI\VEN_8086&DEV_51BC&SUBSYS_899B103C&REV_01\3&11583659&1&E0
Device manufacturer: INTEL
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\alderlakepch-psystem.inf_amd64_c27bc8858e991c72\alderlakepch-psystem.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) Power Engine Plug-in
Device instance path: ACPI\INT33A1\1
Device manufacturer: Intel Corporation
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\intelpep.inf_amd64_d7f0672e6c9d771e\intelpep.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) Graphics Command Center
Device instance path: SWD\DRIVERENUM\IGCC&4&8A18F95&0
Device manufacturer: Intel Corporation
}
All matching/supported Driver Store INF files:
{
INF file path: "C:\Windows\System32\DriverStore\FileRepository\igcc_dch.inf_amd64_4b6e72c945d3dca7\igcc_dch.inf"
INF file date: "07/08/2024"
INF file version: "32.0.101.5763"
INF Models Section: "IntelGfx.NTamd64.10.0...17763"
INF Models Entry: "Intel(R) Graphics Command Center = IGCC_Component_Install,SWC\101.5763_VEN8086_IGCC"
}
INF file in use by device:
{
INF file path: "C:\Windows\System32\DriverStore\FileRepository\igcc_dch.inf_amd64_4b6e72c945d3dca7\igcc_dch.inf"
INF file date: "07/08/2024"
INF file version: "32.0.101.5763"
INF Models Section: "IntelGfx.NTamd64.10.0...17763"
INF Models Entry: "Intel(R) Graphics Command Center = IGCC_Component_Install,SWC\101.5763_VEN8086_IGCC"
}
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) Host Bridge/DRAM Registers - 4609
Device instance path: PCI\VEN_8086&DEV_4609&SUBSYS_899B103C&REV_04\3&11583659&1&00
Device manufacturer: INTEL
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\alderlakesystem.inf_amd64_0565e3956cec3231\alderlakesystem.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) SPI (flash) Controller - 51A4
Device instance path: PCI\VEN_8086&DEV_51A4&SUBSYS_00000000&REV_01\3&11583659&1&FD
Device manufacturer: INTEL
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\alderlakepch-psystem.inf_amd64_c27bc8858e991c72\alderlakepch-psystem.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) LPC Controller - 5182
Device instance path: PCI\VEN_8086&DEV_5182&SUBSYS_899B103C&REV_01\3&11583659&1&F8
Device manufacturer: INTEL
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\alderlakepch-psystem.inf_amd64_c27bc8858e991c72\alderlakepch-psystem.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) Innovation Platform Framework Manager
Device instance path: ACPI\INTC1041\IETM
Device manufacturer: Intel
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\ipf_acpi.inf_amd64_d8fafa4e2f98ceba\ipf_acpi.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel(R) Serial IO I2C Host Controller - 51E9
Device instance path: PCI\VEN_8086&DEV_51E9&SUBSYS_899B103C&REV_01\3&11583659&1&A9
Device manufacturer: Intel Corporation
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\ialpss2_i2c_adl.inf_amd64_563fbcd35feb69a6\ialpss2_i2c_adl.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Realtek Audio Universal Service
Device instance path: SWD\DRIVERENUM\{C3A63EDD-2D27-4B66-B155-5E94B43D926A}#REALTEKSRV&6&26300440&0
Device manufacturer: Realtek
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\realtekservice.inf_amd64_006af324e692be1e\realtekservice.inf
All matching Installer INF files: "NULL"
}
{
Device
{
Device name: Intel® Smart Sound Technology for Bluetooth® Audio
Device instance path: INTELAUDIO\CTLR_DEV_51C8&LINKTYPE_03&DEVTYPE_00&VEN_8086&DEV_AE30&SUBSYS_8D56103C&REV_10EC\5&161EAF8F&0&0000DIF_000A&UIF_0000
Device manufacturer: Intel(R) Corporation
}
All matching/supported Driver Store INF files: "NULL"
INF file in use by device: C:\WINDOWS\System32\DriverStore\FileRepository\intcbtau.inf_amd64_a6c51285c2c72b62\intcbtau.inf
All matching Installer INF files: "NULL"
}
}
||
2025/10/18 13:05:34.546|INFO|
Components:
{
Intel® Graphics Driver, InstallerVersion = Unavailable, ExistingVersion = Unavailable
oneAPI Level Zero, InstallerVersion = 1.24.1, ExistingVersion = Unavailable
Intel® Driver Support Assistant, InstallerVersion = 25.4.36.6, ExistingVersion = Unavailable
Intel® Computing Improvement Program, InstallerVersion = 2.4.11001, ExistingVersion = Unavailable
Intel® Endurance Gaming, InstallerVersion = 1.8.465.30, ExistingVersion =
Intel® Graphics Software & Drivers Uninstaller, InstallerVersion = , ExistingVersion =
Intel® Graphics Software, InstallerVersion = 25.32.1758.2, ExistingVersion = Unavailable
}
||
2025/10/18 13:05:34.546|INFO|Checking for other driver installations, not triggered by the installer. ||
2025/10/18 13:05:34.546|INFO|No other driver installations. ||
2025/10/18 13:05:34.546|INFO|Blocking Windows Update... ||
2025/10/18 13:05:34.650|INFO|Blocking Windows Update - DONE ||
2025/10/18 13:05:34.885|INFO|The driver is signed correctly. Path = "C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\DisplayAudio\12.1\IntcDAud.inf". Details: "The operation completed successfully."
The driver is signed correctly. Path = "C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\MSHdaDac.inf". Details: "The operation completed successfully."
The driver is signed correctly. Path = "C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\iigd_dch.inf". Details: "The operation completed successfully."
The driver is signed correctly. Path = "C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\HdBusExt.inf". Details: "The operation completed successfully."
The driver is signed correctly. Path = "C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\CtaChildDriver\CtaChildDriver.inf". Details: "The operation completed successfully."
The driver is signed correctly. Path = "C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\GSCAuxDriver.inf". Details: "The operation completed successfully."
The driver is signed correctly. Path = "C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\gscheci.inf". Details: "The operation completed successfully."
The driver is signed correctly. Path = "C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\memcntrl.inf". Details: "The operation completed successfully."
The driver is signed correctly. Path = "C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\I2CDriver\Intel_NF_I2C_Child.inf". Details: "The operation completed successfully."
The driver is signed correctly. Path = "C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\iigd_dch_d.inf". Details: "The operation completed successfully."
The driver is signed correctly. Path = "C:\Users\charl\AppData\Local\Temp\RarSFX0\Graphics\PmtChildDriver\PmtChildDriver.inf". Details: "The operation completed successfully."
||
2025/10/18 13:05:34.885|INFO|
Files in Extras folder.
{
C:\Users\charl\AppData\Local\Temp\RarSFX0\Resources\Extras\EgHwProbeApp.exe,
C:\Users\charl\AppData\Local\Temp\RarSFX0\Resources\Extras\EgHwProbeWrapper.dll,
C:\Users\charl\AppData\Local\Temp\RarSFX0\Resources\Extras\EnduranceGaming-Official.1.8.465.30.msi,
C:\Users\charl\AppData\Local\Temp\RarSFX0\Resources\Extras\Intel-Driver-and-Support-Assistant-Installer.exe,
C:\Users\charl\AppData\Local\Temp\RarSFX0\Resources\Extras\IntelGraphicsSoftware_25.32.1758.2_Release.exe,
C:\Users\charl\AppData\Local\Temp\RarSFX0\Resources\Extras\ipfcoresdk.dll,
C:\Users\charl\AppData\Local\Temp\RarSFX0\Resources\Extras\oneAPI_Level_Zero-1.24.1-win64.msi,
C:\Users\charl\AppData\Local\Temp\RarSFX0\Resources\Extras\WIN_DCA_2.4.0.11001_sursvc_qh.msi
}
||
2025/10/18 13:05:35.345|INFO|Extras digital signature check took 0.452387 sec. ||
2025/10/18 13:05:35.345|ERROR|Could not find driver file. ||
2025/10/18 13:05:35.345|INFO|FW update service prerequisites check... ||
2025/10/18 13:05:35.345|WARN|No supported devices by the driver. Skipping FW update service prerequisites check. ||
2025/10/18 13:08:00.869|INFO|Closing the user interface window. ||
2025/10/18 13:08:00.889|INFO|Restoring "wuauserv" service original state and settings... ||
2025/10/18 13:08:00.899|INFO|Restoring "wuauserv" service original state and settings - DONE ||
2025/10/18 13:08:00.899|INFO|Exiting application with exit code: 8. Error, installer could not find correct driver which matches devices on the system. ||
2025/10/18 13:08:00.899|INFO|Logging completed on 2025/10/18 13:08:00.909
||

I was really hoping this would work.

[AlHill]

@Chuck101   I hate to be the bearer of bad news, but no one is going to read a post this long.

And, you really need to remove your email address in your previous posts.

Doc (not an Intel employee or contractor)
[CoPilot is a virus]

[Chuck101]

Okay, how do I remove my email address from the previous posts?

Why am I unable to view live streaming video from my security cameras on Win 10 Home but not on Win 11 pro using EseeCloud?  What changed?

Thanks.

[AlHill]

You can edit your previous posts.  Use the 3 vertical dots next to thee specific post and select edit.

Your eseecloud issue sounds like something you should discuss with Microsoft.  They know what changed from w10 to w11, home and pro.

Doc (not an Intel employee or contractor)
[CoPilot is a virus]

[Chuck101]

Howdy,

Your three vertical dots may have an edit option but mine does not.  I've hunted all over the site for any three dots showing an edit function, but I must be on the island of misfit old guys, because I don't show one anywhere.

I agree this seems to be an MS problem and I have yelled at them.  So, in the interim I will continue to use my old HP running Win 10 home to do the job.

Thanks again.

Chuck

[AlHill]

Look here:

Doc (not an Intel employee or contractor)
[CoPilot is a virus]

[Chuck101]

Yup, I have no edit button....

Thanks.  I agree, CoPilot is a virus.

[ZER0C00L]

Not happy to say Hiseeu is a huge waist of time. I swear they made everything as clunky, slow, & complicated as possible to wear me down so I'll give in to using their cloud storage. I can live view & playback direct with nvr on my win11 after many issues. but the interface is far from user friendly & my bit rate is locked at such a low value it's almost not worth viewing live feed. Sure it's to reduce connectivity issues & save storage space, but what if these aren't issues for me & i wish to prioritize for quality. well yeah, it's better viewing after offloading, but the interface only allows offloading 1 camera at time for 1 day at a time. Plus 1 day of 1 cameras video is spread across 10 pages as clips that have to be selected individually: click 10 boxes on 1st page, change to page 2 click next 10 boxes, etc... & then repeat times 6 cameras just for a single day of footage. Hit offload expecting a popup to select a folder location, but instead i get a 60second countdown with message saying to plug in a storage device to the nvr usb port!? Why the count down? Will it self destruct? Does the usb need to be a particular format? Does it need to be blank? Oh well, no time... & also NO USB PORT! except where the mouse is plugged in which am using to navigate the interface. It's a lovely design & can hardly wait to see which will break 1st, me from doing this 6 times a day, or the mouse/usb flashdrive/nvr from the number of unnecessary unplug  & re-plugging. Kudos Hiseeu, ya got me. I'll bet the bulk of their employees work in costumer service, but unfortunately their service is sub-par also. Sure i got  a quick response, just to be given a general process of elimination not even related to the password issue i was reporting at that time. I did at least find a video guide for using the EseeCloud CMS software. It's titled "How to Download EseeCloud Virus". Not sure if this is a translation error or what, but it's a perfect title.

[Chuck101]

I feel your pain.  My issue is that Eseecloud will not show live video for any camera using a brand NEW HP laptop running Win 11 Pro.  I am stuck using my old HP laptop running Win 10 and I am using EseeCloud Ver 3.07.10, which works great running Win 10.  The video feed H265 (I think) can't get past Win 11 Pro for some stupid reason.

It has been suggested to me that I run Eseecloud in compatibility mode, duh, but Win 11 Pro doesn't offer such an obvious solution.  It has also been suggested I run the Android version using an emulator.  Sure and maybe brick my computer, no thanks.

Intel has an "update" that should fix the problem, but it doesn't support my chip.  Way to go Intel.  HP is no help.

I've complained to Hiseeu about Eseecloud asking for patch or something....maybe something from this century but was told since so few people use Eseecloud they have no intention of upgrading the software.  Sucks to be a new customer.

Hiseeu does have a work around using your browser, you can get the live video but as with the NVR it sucks trying to download any video.  You can download a live feed which works okay or watch one or several cameras at a time.  Try: https://v.dvr163.com/?type=hiseeu#/login

If you are trying to use the NVR to handle the cameras and downloads it really doesn't work.  You really need EseeCloud to work.

1.  Find a computer still running Windows 10.

2.  Load Eseecloud V 3.07.10 which works better than the other available versions I've tried.  You can get it from support at Hiseeu.

3.  Assuming it loads up you'll need to set it up.

 a. there is no password so just log in

 b. upper right hand corner hit the add button

 c. it will ask for the IP/DDNS of the NVR, such as 192.168.1.**bleep**, enter the address tab to password

 c. enter the password you use to connect to the cameras, used by the NVR, tab to device name

 d. whatever device name you use, mine is simply Home, they consider the NVR and all the cameras as a device

 e. enter the number of channels which is how many cameras are connected the NVR, mine is at 8, I have room for 2 more

 f. that should get you into the program check the buttons on the bottom that should work now.  Continue the setup.

 g. the documentation is not the best I've seen but download it and follow the setup.  Eseecloud does work well in conjunction with the phone app.  

The phone app will receive the alerts generated by the cameras and you can view them right quick.  In fact if the action is of interest you can go to live view and record it to the phone but if you download to your phone you'll have to upload to your mailbox if you want to save it somewhere. Or, if Eseecloud is running you can save it there to your local storage. I have a NAS so all downloaded video is there and on the NVR the difference being the NAS has actual named files (by me) whereas the NVR file name will be: admin date time camera chan.mp4.  All downloaded video is mp4.

This is how I do it.  I do not use the NVR other than setting up cameras and such.  I use the phone app to monitor the system and cameras.  I can move cameras as needed (PTZ cameras), I can adjust sensitivity, turn alarms on/off, in general I run the system.   So, when I have a bunch of alerts, I go to the app (or EseeCloud on the laptop),  I select one camera of interest and review the clips and decide which one to keep.  I then go to EseeCloud, select playback, select a camera, and select download.  I then have a very nice list of clips in chronological order.  I can select one or a group, I can even download a whole days' worth if I want.  That is why I need EseeCloud to work.  The NVR will keep all of them but you can not see the NVR hard drive.  It would really be nice to see it as attached storage but not to be.  I believe the files are encrypted anyway.  Right now my system has been up for 18 months and the NVR is at 20% capacity.  This is the reason I have no interest in the "cloud".  I can go back to day one and search for a video clip with no need to beg the company for some video

Now, about the USB port. I think they are referring to the USB camera port.   Each camera has a port for a mem card, I think 128Meg.  If you don't have an NVR this is where your recordings will be.  You have to supply the mem cards.  Using Eseecloud or the phone app you should be able to access the card and download video.  None of my cameras have a mem card.  I do have 1Terabyte of NVR storage, which is why I bought the bloody thing.

The equipment works well enough for my purposes it is the software that sucks along with the fact it won't run on Win 11 Pro.  The website should take you to the support page for the manual and the app.  The phone app should be available through your phone.

https://www.hiseeu.com/pages/app

I hope I helped some.  

[Chuck101]

"I can live view & playback direct with nvr on my win11 after many issues...."

I just re-read your post and noticed that you have EseeCloud running in Win 11??????  How did you manage that????

What did you do in Win 11 to make it run???

[ZER0C00L]

the simple answer is that i used Google's new assistant Gemini on my phone. there's the "fast" model that gives quick shorter responses, & there's a "thinking" model that shows the thought process & responds with more detail. it often goes through a multi-step process of elimination that sometimes feels like just hitting failed dead ends, but it does this trying to find what will fix the problem without  causing others.  if you give it plenty of the specifics about your hardware & setup plus your intended goal, it can sometimes find  a quicker solution without having to browse through many resources & research each detail on your own. my hardware is completely different from yours so it could be a number of things since i'm on desktop pc with Prime z790-p mobo & rtx 4070 gpu. also i have windows home version & not pro . even though one would think pro version would have more available. this might actually cause a problem when we're talking about anything that involves Hiseeu. i'm not sure how i could help, if at all, other than to suggest trying an ai model that solves problems like this. i'm used to using github & discord for community help with most my issues but don't know of any Eseecloud help on these platforms. i'm actually returning all my Hiseeu hardware today because yesterday while viewing some playback with Eseecloud my nvr internal speaker made a "POP" & screen went black, then "no signal" message. nothing i did would recover the nvr & all light indicators stuck on solid as soon as plugged in. maybe a capacitor? can't say, but am done with Hiseeu for sure!

[Chuck101]

You may be right; it just might be a Win 11 Pro issue.  I spent a bunch of money for a new HP Laptop with Win 11 Pro and a simple program won't run and everyone appears to be clueless.

Sorry to hear about your gear going belly up, maybe something in the hardware was the problem all along. 

Take care and good luck on your next system.