I was updating software on my computer in anticipation of doing imaging in the next week or two. I was upgrading from 3.2.6383 which worked fine. Love your product by the way. I clicked on 'Check for updates' which downloaded 3.2.6473, and then clicked on 'Install and Relaunch' After Install, it went to relaunch, the startup banner came up, disappeared, but Sharpcap did not start up. I tried installing previous versions to see what would work. The latest version that works on my computer is 3.2.6421.
I reinstalled 6473 and reran from command line with 'dump' option which is attached.
I last updated Win 10 2/12/2021. I am running Win 10 v2004 OS Build 19041.685. .Net 4.8
I am using ZWO ASI290MC and ASI294MC Cameras
Computer is a Dell with i7 chip.
The log is empty.
Dump File:
https://1drv.ms/u/s!AhuY4v-yKKBqjRWufGU ... W?e=MuGJXc
Let me know if you need more information
Looking through the forum, I found a couple of other things to try:
Shift - Start SharpCap to get log file:
Turned off anti-virus AVG.
Ran Shift - Start SharpCap again log had same information
Ctrl-Shift - Start SharpCap
Results: _enabling Lauhch Port
Stage 1 complete
Stage 2 complete
Stage 3 True
Stage 4 True
Stage 5 True
Full Trust?: True
Stage 6 True
Launch page comes up then nothing. Log file empty.
Sharpcap 3.2.6473 will not start
Forum rules
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
Please also read about Troubleshooting USB Issues before posting.
*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***
Please include the following details in any bug report:
* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
- admin
- Site Admin
- Posts: 13362
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Sharpcap 3.2.6473 will not start
Hi,
I think the problem is this one – viewtopic.php?t=3649
Can you try the suggested solution there and see if it fixes the problem please?
Thanks, Robin
I think the problem is this one – viewtopic.php?t=3649
Can you try the suggested solution there and see if it fixes the problem please?
Thanks, Robin
Re: Sharpcap 3.2.6473 will not start
Thank you for looking into this. It has been a while since I've had to admin Win, Win 7 was the last release. I forgot about event viewer. It was a frustrating part of my career, and have tried to put Win OS behind me. Unfortunately, There are a couple of products for imaging and processing that I like too much that run on Win, like SharpCap.
I doubled checked the errors in the EV and they were exactly the same. Performed the Regedt, and it works fine. Thank you for your time. Love your product and recommend it to my club. Keep up the good work.
Art
I doubled checked the errors in the EV and they were exactly the same. Performed the Regedt, and it works fine. Thank you for your time. Love your product and recommend it to my club. Keep up the good work.
Art
- admin
- Site Admin
- Posts: 13362
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Sharpcap 3.2.6473 will not start
Hi,
Glad to hear that that worked I've now fixed this problem in the code, so there is an update to 3.2 that shouldn't need the registry fix in case it happens to someone else.
Cheers, Robin
Glad to hear that that worked I've now fixed this problem in the code, so there is an update to 3.2 that shouldn't need the registry fix in case it happens to someone else.
Cheers, Robin