Repeated Hyper-V and MS SQL Server instance checks?

I just noticed this while looking into something else - is there a reason we’re checking for MS SQL Server instances and Hyper-V more than once? Could it be because I have 6 drives (3 physical, 1 optical, and 2 UNC mappings) and it’s trying to check each non-optical drive letter?

Apr 16, 2018 10:38 PM: Cannot open WMI provider \\localhost\root\virtualization\v2. Hyper-V is probably not installed.
Apr 16, 2018 10:37 PM: Cannot find any MS SQL Server instance. MS SQL Server is probably not installed.
Apr 16, 2018 10:34 PM: Cannot open WMI provider \\localhost\root\virtualization\v2. Hyper-V is probably not installed.
Apr 16, 2018 10:34 PM: Cannot find any MS SQL Server instance. MS SQL Server is probably not installed.
Apr 16, 2018 10:33 PM: Cannot open WMI provider \\localhost\root\virtualization\v2. Hyper-V is probably not installed.
Apr 16, 2018 10:33 PM: Cannot find any MS SQL Server instance. MS SQL Server is probably not installed.
Apr 16, 2018 10:32 PM: Cannot open WMI provider \\localhost\root\virtualization\v2. Hyper-V is probably not installed.
Apr 16, 2018 10:32 PM: Cannot find any MS SQL Server instance. MS SQL Server is probably not installed.
Apr 16, 2018 10:30 PM: The operation Backup has started
Apr 16, 2018 10:16 PM: Cannot open WMI provider \\localhost\root\virtualization\v2. Hyper-V is probably not installed.
Apr 16, 2018 10:16 PM: Cannot find any MS SQL Server instance. MS SQL Server is probably not installed.

I have not developed or used that feature, maybe mnaiman can answer, but I don’t hink he is on the forum?

A post was split to a new topic: Backups to FTP no longer working