[SOLVED] Fail to upgrade Windows 7 to Windows 10 – error 0xC1900101 - 0x40017

Should I disconnect everything else in Device Manager console? There's not much I can disconnect. Card reader, camera, Bluetooth, audio.
 
Ok, that should be fine.
There is communication software installed for smartphones by Nokia and Huawei.
Do you still use both ?
 
Ok, that should be fine.
I'm not sure if that means I can disconnect devices (post #41) or update drivers (post #42) or both...
There is communication software installed for smartphones by Nokia and Huawei.
Do you still use both ?
No, I don't. I just uninstalled them both. And FreeCam, Skype and something else I can't remember now.
 
I just uninstalled them both. And FreeCam, Skype and something else I can't remember now.
If the upgrade still isn't successful, perform a new scan with FRST:

FRST Scan:
  1. Right-click to run FRST64.exel as administrator. When the tool opens click Yes to disclaimer.
  2. Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
  3. Press the Scan button.
  4. Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
  5. Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.
 
Not yet. You have a Canon printer installed.
There is also a part of a Hewlett-Packard printer installed. Can that be a remnant of a Hewlett-Packard printer ?
 
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.

Step 2:
Only if there are drivers in Device Manager with an yellow exclamation mark or red cross that needs attention.
 

Attachments

Uninstall OpenVPN 2.3.13-I001.
Reboot the machine
Try the upgrade again and report the result.
 
Uninstalled OpenVPN, also it's associated TAP-Windows. Restarted machine and tried upgrade, but it failed again with the same error code :(

I uploaded:
  • SetupDiag's scan files: SetupDiagResults.log and Logs.zip
  • FRST.exe scan files: FRST.txt and Addition.txt
  • zipped C:\Windows\Logs\CBS folder
  • C:\$Windows.~BT\Sources\Panther\setupact.log
  • C:\Windows\INF\setupapi.dev.log
to /Dropbox/post#52. Just in case you asked for them.
 
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.

Step 2:
Open the File Explorer, click This PC, and select Properties.
Click Advanced system settings.
Click Advanced tab.
Click the button Settings in the third frame.
A new window opens. Provide a screenshot of that window.
 

Attachments

The settings in the screenshot are OK.

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.
 

Attachments

Fixlog.txt uploaded to /Dropbox/post#56.

What about the hacktool that you were talking about before?
If the system was illegal, can it be that the upgrade fails but it wouldn't say anything about the legal/illegal system? I thought it would say something
 
If the system was illegal, can it be that the upgrade fails but it wouldn't say anything about the legal/illegal system? I thought it would say something
You'll never know with hacktools.
This is what I noticed in the logs:
Code:
S2 KMService; C:\Windows\SysWOW64\srvany.exe [8192 2014-09-20] () [Brak podpisu cyfrowego]


Open the File Explorer, click This PC, and select Properties.
Click Advanced system settings.
Click Advanced tab.
Click the button Settings in the first frame.
Click Advanced tab.
In the frame Virtual memory, click Change.
A new window opens. Provide a screenshot of that window.
 
The screenshot doesn't show something wrong.
I'll try to investigate on this exe.
That is not needed as we already removed the service in a previous fix.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top