Windows 11 Installation Problem

[WxObserver]

Installing the trial version on a Windows 11 laptop. The resulting install folder is not visible in Explorer, but can be seen from Powershell. I can start the app from powershell, but when trying to activate, it says that a required service is not installed.

[WxObserver]

Okay. Fixed.

Could not even find the log files. Pulling my hair out -- how can there be files I cannot see???

Then I realized -- it's the friggin' sandbox. Somehow, I don't know how, the antivirus sandbox got turned on (I specifically keep that turned off), and the installer got sandboxxed, which means anything it installed was also sandboxxed.

At that point, only sandboxxed programs could see those files and somehow the 7-zip file manager got sandboxxed too.

BYE is installed and license activated now. Jeez, what a circus, none of it your fault of course.

Sorry about all the confusion, but windows sucks, and that's one reason why. At least now if you hear about invisible files maybe you can remember to suggest that they got sandboxxed.

[WxObserver]

Tried renaming the folder in powershell and no help.

Ran the install again and now I cannot even see the folder in powershell, but the installer is the only thing that seems to be able to see it. This is the current version -- 3.2.3

Note, this laptop has dual boot for Win 7 and Win 11, and it is booted into Win 11, if that matters.

[admin]

Where are you installing it? Default location?

 

[astroman133]

Just to clarify...Trial is a license type, not a version. The version is a dotted-decimal number like 3.2.3 or 3.5.0.RC7.

What version did you install? Was it the x64 version of 3.5.0.RC7? This would have a different default installation folder than the 32-bit version.

If you are looking in the right location and cannot see a folder, then it seems like a privilege issue. If you chose a "hidden" folder location to install BYE then you might not be able to see it from Windows Explorer. The following link may provide some additional info.

https://support.microsoft.com/en-us/windows/view-hidden-files-and-folders-in-windows-97fbc472-c603-9d90-91d0-1166d1d9f4b5

 

[WxObserver]

13 minutes ago, astroman133 said:

Just to clarify...Trial is a license type, not a version. The version is a dotted-decimal number like 3.2.3 or 3.5.0.RC7.

What version did you install? Was it the x64 version of 3.5.0.RC7? This would have a different default installation folder than the 32-bit version.

If you are looking in the right location and cannot see a folder, then it seems like a privilege issue. If you chose a "hidden" folder location to install BYE then you might not be able to see it from Windows Explorer. The following link may provide some additional info.

https://support.microsoft.com/en-us/windows/view-hidden-files-and-folders-in-windows-97fbc472-c603-9d90-91d0-1166d1d9f4b5

 

Version is 3.2.3. This looks like a cool app, and I would probably purchase full version if it would install properly...

I have tried both the default install location (in Program Files (x86)) and other manually specified locations. Is there a 64-bit version I could try? What's the link to that?

This happens on two different laptop computers with Win 11 now.

The folder isn't "hidden" -- that is the option to show hidden folders in Explorer is enabled, from powershell dir -Hidden doesn't help. I can still see and browse the folder in 7-zip file explorer, but not in powershell or Windows Explorer.

I can run the BinaryRivers....longname...Camera1.exe file from 7-zip explorer, and a dialog pops up for the license key. When I enter that, the error shown below pops up.

I've installed lots of apps on both of these Win 11 laptops and never had any problems like this before.

Tried searching on folders not showing in Explorer or powershell and nothing found there helps.

I'm not a computer idiot and there's something really weird going on here that I have not seen before.

[WxObserver]

I also tried switching the dual-boot laptop to Win 7, and the program installs there without any problems. Have not tried activating it on Win 7 as I really need to run this on Win 11 in the long term.

[WxObserver]

Okay, found the 3.5.0.RC7 x64 version, and it's got the same problem. Install folder only visible from 7-zip file explorer, and running the ....Camera1.exe file gets the same validation error shown above.

[astroman133]

Now I am very confused. The only way that you would be able to see the BYE License Validation dialog is by running the BYE program. If you are able to run the program then it must have installed correctly. In that case you must be able to view the installation folder.

The dialog that you are seeing is NOT a validation error. It is a request for you to enter the needed information.

In order to run the program you MUST enter a license key and your Identifier (the username of the account that you used when you "purchased" your license) into the license validation dialog when prompted to do so. After you enter the Trial license key the program will run for 30 days. After that you will need to purchase a permanent Classic or Premium license. This paid license will never expire. Also, when using a Trial license, BYE will phone home, using your internet connection, each time you launch it. This verifies that the license has not expired.

I put the word 'purchased' in quotes above because a Trial license is free, but you still have to go through the O'Telescope store in order to get the key issued to you. Once you do, the key is available from the web site. Just scroll to the top of the web page where you are reading this reply and select My Purchases -> Orders from the blue menu bar.

You should use Copy and Paste to transfer your Trial or permanent license key from the web site into the license validation. It is not recommended to try to manually type the license key into the validation dialog.

Oh, and do not post a screenshot of the License Validation dialog once you have entered in the license key. Posting your key in any public forum or site, including this site, is grounds for invalidation of your license, per the O'Telescope owners.

Also, in order to validate your license, BYE contacts the O'Telescope servers. Those servers use the latest in internet security and it is likely that if you have BYE running on  Windows 7  that the license will be successfully validated. This is why Windows 7 is no longer supported by O'Telescope.

Also, it is up to you to make sure that BYE can actually control your camera. Some very old cameras are no longer supported, and very new cameras may not be supported yet. It is also possible that Canon chose not to support tethering for your model, as they did for some of the earliest mirrorless models. Look at the Supported Cameras page on this site for details. A link is in the footer at the bottom of this page.

There are also several other possible gotchas...

• If the camera supports wireless communication, it must be disabled. Instead you must use a USB cable that is connected between the camera and the PC.
• Only a single application at a time can be connected to the camera.
• Some newer cameras have a setting that prevents BYE from taking pictures unless the camera senses that a lens is mounted on the camera. If you want to take pictures (for testing purposes) with the body cap in place, this setting must be changed. Also if you want to take pictures through a telescope, the setting must be changed.
• In order to use Frame & Focus or Planetary imaging modes, LiveView must be enabled in the camera.

I hope this helps.

[WxObserver]

Okay, sorry but I didn't provide a totally clear post there.

That dialog shot has the license key and user ID blurred out (did that in Photoshop) -- as I was warned that posting the key would cause it to be disabled. This dialog shows what happened AFTER I entered the key and ID and pressed the Validate button. There are actually valid key and ID fields entered there.

Also, to be very clear, I had to run the BYE program by navigating to the install folder with 7-zip file manager. The desktop icon and start menu folder either failed to install or are not visible for the same reason that Windows file explorer cannot see the install directory.

To summarize, there seem to be two problems:

1) The installed files aren't visible to Windows -- I must use 7-zip file explorer to see them.

2) The validation tool returns the error I posted above when the license key and ID are entered -- specifically "The specified service does not exist as an installed service." I suspect that if the installation is trying to create a Windows Service, that has failed for the same reason that is causing problems in (1).

It's possible that (2) is a consequence of (1).

I have tried looking at, and playing with security permissions on the installation folder and files, and I don't see anything obviously wrong there.

Can't help but think there's something funny about attributes or permissions on the installation but haven't had any luck in figuring that out.

I take it nobody else has run into this before...?

[admin]

1 hour ago, WxObserver said:

hat dialog shot has the license key and user ID blurred out (did that in Photoshop) -- as I was warned that posting the key would cause it to be disabled.

Thank you for not posting your key in a public forum.

Try installing in c:\BYE folder instead of the default program files folder.

 

[WxObserver]

Okay, tried that, install to C:\BYE, but same problems,

(a) Only 7-zip file manager can see the install folder

(b) No desktop shortcut or start menu folder

(c) Same validation error when running the app from 7-zip file manager.

Since the error seems to indicate a needed windows service isn't running, I looked in the services manager (services.msc) and could not spot any newly added services. Maybe I missed one, but there wasn't anything obvious. Of course, I'm just guessing about the error message, but that's all I can offer at this point.

[astroman133]

Are you sure that you ran the installer program to unpack the application? If you try to run BYE while it is still inside of the installer then that could cause some strangeness, like what you are seeing.

You should download the installer from the O'Telescope web site to your typical file download folder then double-click on it to launch it and to unpack and install the application. This should put a shortcut on your desktop to launch BYE and to add it to the Windows Start menu.

[admin]

in 14 years since I released BYE I have never seen this behaviour. BYE uses InnoSetup to create the setup.exe package, and there is no special gymnastic, everything is boilerplate setup. I'm stump.

[admin]

 

Send me the log file.

 

 

 

[WxObserver]

No, the installer finished before I tried to run the app. The installer presented a "finished" dialog and I clicked a button to close the installer. Here's my process in detail:

1) Download the installer (either 3.2.2 x86 or 3.5.0.RC7 x64) to the hard drive

2) Run the installer from the local hard drive.

3) Specify the destination folder (C:\BYE), accept the suggested start menu folder, and desktop icon.

4) Finish running the installer. It says it finished successfully.

It's only at this point where I look to see the seemingly failed results.

There are many computers around here, and I just tried it with a Win 10 desktop -- no problems. This really looks like a Win 11 problem.

I'll be glad to send you log files...I presume you want me to enable installer log files and re-run the installation?

[admin]

It's not a w11 problem, I've been on w11 since it was released, and my development environment is exclusively W11. There is something else at play here.

[admin]

6 minutes ago, WxObserver said:

I'll be glad to send you log files...I presume you want me to enable installer log files and re-run the installation?

No, send me the BYE log file as per instruction. You do get a service error in BYE and I want to know if it's coming from within BYE.

[admin]

15 hours ago, WxObserver said:

Okay. Fixed.

Could not even find the log files. Pulling my hair out -- how can there be files I cannot see???

Then I realized -- it's the friggin' sandbox. Somehow, I don't know how, the antivirus sandbox got turned on (I specifically keep that turned off), and the installer got sandboxxed, which means anything it installed was also sandboxxed.

At that point, only sandboxxed programs could see those files and somehow the 7-zip file manager got sandboxxed too.

BYE is installed and license activated now. Jeez, what a circus, none of it your fault of course.

Sorry about all the confusion, but windows sucks, and that's one reason why. At least now if you hear about invisible files maybe you can remember to suggest that they got sandboxxed.

Thanks for letting us know.

And for a good laugh, sorry, I couldn't resist, lol.