S Sysnative Windows Update Inactive Joined Oct 9, 2014 Posts 773 Sep 10, 2019 #21 If a file was corrupt, the tool(s) would report it. We checked and the logs were clean. Therefore, it's not a corrupt file. Maybe the driver for the external enclosure/dock is giving you grief?
If a file was corrupt, the tool(s) would report it. We checked and the logs were clean. Therefore, it's not a corrupt file. Maybe the driver for the external enclosure/dock is giving you grief?
A amadev Well-known member Joined Aug 20, 2019 Posts 62 Location sydney Sep 10, 2019 #22 softwaremaniac said: If a file was corrupt, the tool(s) would report it. We checked and the logs were clean. Therefore, it's not a corrupt file. Click to expand... No file corruption and no error in the trace yet there are errors logged. The Phone and Modem CP says "You may have a problem starting telephony service" but the service is running and so are all its dependencies. The home group services are both running but when trying to connect the error says that it can only connect to a home network yet it is a home network. So whatever data it's getting, although not corrupted, it is the wrong data. softwaremaniac said: Maybe the driver for the external enclosure/dock is giving you grief? Click to expand... Just a standard USB3 dock. It was working fine until I disabled and re-installed the network adapter driver while trouble shooting. I'll get around this later. Separate issue.
softwaremaniac said: If a file was corrupt, the tool(s) would report it. We checked and the logs were clean. Therefore, it's not a corrupt file. Click to expand... No file corruption and no error in the trace yet there are errors logged. The Phone and Modem CP says "You may have a problem starting telephony service" but the service is running and so are all its dependencies. The home group services are both running but when trying to connect the error says that it can only connect to a home network yet it is a home network. So whatever data it's getting, although not corrupted, it is the wrong data. softwaremaniac said: Maybe the driver for the external enclosure/dock is giving you grief? Click to expand... Just a standard USB3 dock. It was working fine until I disabled and re-installed the network adapter driver while trouble shooting. I'll get around this later. Separate issue.