Gronaldo

After more testing I found a reboot is required in order to work. Machine is usually off and active for making backups, as target for live Nas and creating secondary backup to USB drive. So after initial boot, no USB drive is detected, even after reconnecting a few times. After reboot, with drive connected, is works. Any suggestions how to resolve or what issue may be? Thanks for any assistance .

For a long time I am using a Seagate USB 3.0 drive for external backups. It seems starting with DSM 6.1.7-15284 the drive is no longer recognised. Test with other USB 3.0 drives have same results. On USB 2.0 all drives do work. I am using same hardware, same loader (Jun v.1.02b) as before, when all worked without any issues. Anybody any suggestions how to fix this? Many thanks!

Nevermind.

I always learned it is never to late to provide feedback. I appreciate the work done, don't get me wrong. But my experiences working for some time with current setup triggered me on this comment. It's easy to criticise, rather than to contribute or create, i know. Nevertheless i hope it may be of use for the future. Thanks.

A bit lost... Sorry to say that i am a bit lost on the new forum. So many categories, so may closed topics, so many branches... Really struggling to find info, and missing the easy to browse, or being updated after a quick visit... Surely it's difficult to accommodate everyone's preferences, but to me it seems a bit overdone.

Thanks, will take a look. Funny thing is; - Working bootdisks (created earlier or newly in VM with Win1703) cannot be read correctly - Same issues at 3 different PC's (new install 1709 or upgraded earlier versions) - Not USB drive dependent, preparation or partioning done as usual - Used to be able to read bootdisk and edit config files directly, not posible anymore, besides on older Win versions. Very strange....

Sure? Releases

All, after the Windows 1709 update I cannot successfully create or read the USB bootdisk loader, using Win32Imager 1.0. Somehow Windows seems to limit access to the USB device and partitions. Using a previous version of Windows, 1703, even as a VM on the same PC, works all fine. So i found my workaround, but i am surprised not to see any similar issues reported here?

After the 1709 update I cannot create or read the USB bootdisk loader, downgrading to 1703 works fine again. I use Win32imager and used to edit config files on desktop, after creating the USB stick. Still investigating what's going on, but any suggestions are welcome.

Duct tape, permanent marker, curtain.....

I can confirm there can be a difference in mainbord and DSM ports. Seen this on at least 3 boards. Serial number is best to check. Asrock C70M1 is an example.

No luck. Issue persists.

Hm..other build have the same update available, but do not open control panel. Will investigate further along suggested lines.

On one of my 6.02 builds, suddenly the Control Panel opens on every login. Tried to toggle disable Resume option on personal settings a few times, without any luck... On another identical build all works well. Both updates from5.2 to DSM 6.0.2-8451 Update 1, using Jun's v1.01 loader. It is just annoying, not serious

Just remove completely.