@Alex-Sunny sagte in Questions about the ioBroker installation under Windows?..:
Then you could still use the complete Create ioBroker folder as a backup at file level as a backup and if necessary. restore by simply replacing the current folder?
Well, the installer of course installs the service which is linked to the given folder, so the folder is not completely independent.
But honestly, I don't see any reason for creating a folder level backup. It is much better to simply use the BackItUp Adapter and put backups for example in the cloud (or your NAS). Like this you can not only restore the system on Windows but also other platforms (like Docker on Windows / WSL).
I noticed that a network drive that was connected to a drive letter via the normal system environment of Windows 10 cannot be reached in the ioBroker command console. Eg "z:" + Enter already leads to an error message.
Why is that? And how else can you access it?
I can confirm that this is the case. I can't access my network drives from my NAS neither. Most probably it is because the command line is running as a local administrator and thus doesn't have access to network drives. Nonetheless ioBroker of course has access to those paths (AFAIK).
Question: why do you need access to network drives from the ioBroker command line? This command prompt is only supposed to be used for administering ioBroker (e.g. add/remove adapters, configure core settings like multihost, ...).