LOGIN  |  REGISTER
Smart Living Made Brilliant!
CASTLEOS FORUM

HomeCastleHUB

Information, FAQs, Q&As, and everything else related to the CastleHUB can be found here

Background Disappears, Xtra Icon, Missing Drive Messages in this topic - RSS

Gregory Martin
Gregory Martin
Posts: 21


12/17/2016
Gregory Martin
Gregory Martin
Posts: 21
So this morning I was greeted by a solid black background on CastleHUB, as the CastleOS background disappeared, and an extra icon for "Open CastleOS" on the desktop of the CastleHUB.


When looking for the logo to put it back as background, the system complains drive E is missing. Why is there a path to an old legacy drive? Was this installation clean or a clone of another system that had an "E" drive location?


The other questions is why did CastleHUB decide to change appearance all on it's own? Is this related to installer bug you mentioned or is this also normal behavior if the hub is left turned on for few days?


Why are there so many aberrant behaviors with this unit?
0 link
Chris Cicchitelli
Chris Cicchitelli
Administrator
Posts: 3350


12/17/2016
Chris Cicchitelli
Chris Cicchitelli
Administrator
Posts: 3350
Hi Gregory, last night another update was pushed to CastleHUB. It's important to note the CastleHUB is designed to run "headless" (as in, without a monitor connected) and the default user account of "CastleOS" is for the CastleOS app and service to use.

You are welcome to use the CastleHUB for purposes beyond CastleOS, especially with regards to media playback etc., but for that we recommend you create a user account you can log into that CastleOS won't use or change your user settings.
Regarding the E drive, have you at any point connected an external drive to the CastleHUB?
0 link
Gregory Martin
Gregory Martin
Posts: 21


12/18/2016
Gregory Martin
Gregory Martin
Posts: 21
Did not connect any other drives.
I think it would be great to be able to run headless but unfortunately when CastleHUB failed right out of the box, had to connect keyboard and monitor to see what had happened since CastleOS was down. With each of the failures, having a keyboard and monitor has allowed me to see the craziness that's going on and restart the service or view the logs not visible through CastleOS, when it is working.


Doesn't seem headless would be doable with the current behavior but I do see that for some headless would be a great way to hide some of the bugs or strange messages. In my case, I left the monitor and keyboard attached because of the ongoing issues and I still can't use the system yet.
0 link
Gregory Martin
Gregory Martin
Posts: 21


1/11/2017
Gregory Martin
Gregory Martin
Posts: 21
Any explanation other than a recommendation to use this for a media storage space? Reference to an E: drive seems like it might not have been a clean install or was copied from an older installation, which probably explains the logs from before this unit was delivered. Did ZOTAC forget to clean up the Windows 10 image before deployment?
0 link
Chris Cicchitelli
Chris Cicchitelli
Administrator
Posts: 3350


1/18/2017
Chris Cicchitelli
Chris Cicchitelli
Administrator
Posts: 3350
Wanted to circle back on this. The issue you are seeing isn't from the CastleHUB, but rather Windows 10 itself. There was a Windows 10 bug where it wasn't properly cleaning prior updates once installed, and then running out of room to install new updates, thus causes errors. Microsoft issued a patch for this, but it had to go through the complete update cycle before it was able to apply it.

In addition, this isn't a "clean" install by Windows by default. It's a customized Windows image to allow it to run headless. So it won't look identical to a fresh install, but at the same time no old files were left behind in the image. The were newly created by updates running after it was turned on.

Thanks!!
0 link
Gregory Martin
Gregory Martin
Posts: 21


1/22/2017
Gregory Martin
Gregory Martin
Posts: 21
Failure to run sysprep on an image is NOT a Windows issue and CastleHUB is what has the problem.
The install has old stuff in it related to an unclean image. "Customized" to run headless didn't work anyway since the product was broken right out of the box. My point is the "customized" image is not clean and should be so that phantom links and other unnecessary garbage are removed.
0 link
Chris Cicchitelli
Chris Cicchitelli
Administrator
Posts: 3350


1/22/2017
Chris Cicchitelli
Chris Cicchitelli
Administrator
Posts: 3350
If sysprep wasn't used, we wouldn't have been able to manufacture the CastleHUB smile I'm quite confident any files left behind are from current Windows Update operations. There wouldn't be enough spare space on the drive if there were files left over files from the factory smile
0 link