Windows 10: Can anyone in Microsoft fix this problem?

The updates don't work and always come back with the same error every time you retry. Hewlett-Packard - USB - 1/16/2017 12:00:00 AM - 44.0.3748.1716 Install error - 0x80070103

:)

 

Recent windows 10 upgrade and microsoft edge problem

Hi Michael,

The issue may occur due to incompatibility of your driver and corrupted Microsoft Edge. In order for us to assist you, please answer the following questions:

• What troubleshooting steps have you done so far?
• What is your latest OS Build?

In the meantime, regarding your issue with Microsoft Edge, We suggest to follow the steps provided in this article:

Fix Windows Update issues to help resolve your browser issue.

In addition, please click this link:
Fix printer problems in Windows 10 to guide you on fixing your printer concern, The article contains a step-by-step troubleshooting guide.

We look forward to your response.

 

Windows 10 1709 System Restore problems...

That seems to be an attempt at Option 2 in the tutorial, which requires you to
a. Boot to a command prompt (Did you?)
b. You then seem to be mixing steps 3,4 and 5, thus your command is incorrect.

I suggest Option 1 is easier.

If you still have problems, please repost listing each specific step and saying which option from the tutorial you are using. Thanks.

 

Microsoft Edge TLS Security

After trying everything (not a lot of steps) listed in the Microsoft Edge support site, I did a wider search and found this very simple youtube video that fixed it immediately:

For those who prefer not to click links the steps are simple:

1. Click in the Cortana search bar next to the Win 10 Start button

2. Type internet options

3. Select internet options (control panel) from the list

4. Click on the advanced tab

5. Scroll down to the security section

6. Make sure the following are all clicked:
Use SSL 3.0
Use TLS 1.0
Use TLS 1.1
Use TLS 1.2

7. Click apply

8. Refresh the page that was giving the error and it should now connect.

Hope this helps, it was a 30 second fix after hours of pounding my head against the error with the Support site suggestions.