Well, from what I can recollect, I witnessed this problem with connecting Smartphone about November 2015. Eventually, I connected the Smartphone via Wi-Fi link and then promptly forgot about the problem until this month.
What I can recollect, the computer was exceptionally unstable between Autumn 2015 to Summer 2016. I remember having to use repair disk a number of times, to recover from boot failures.
Then, from March 2016, the Windows Update service had stopped, so I used services.msc and computer management to switch off ('enable') several policies and configurations to do with Update, error reporting, customer experience and usb.
To be more specific, I'd changed sometime last spring, the following:
Games UpdateCheck
MobilePC
ScheduleDefrag
DiskDiagnosis
MobilityManager
gwx
Gadget Manager
SvcRestartTask
Disable Reminders
Set Windows File Protections
Hide the file scan progress window
Maximum Retries to unload and update user profile
Set roaming profile path for all users logging onto this computer
Only allow local user profile
Do not forcefully unload the users registry at user logoff
windows boot performance
scripted diagnostics
configure scheduled maintenance behaviour
Configure MSI
Configure Scenario Execution Level
disk diagnostic
configure corrupted file recovery
application compatibility
shutdown options
remote assistance
kerberos
automatic root certificate update
trusted platform module services
microsoft support diagnostic tool
Suppose these changes were not prior to issue on cameraphone, however they were prior to issue on camera failed to connect.