[SOLVED] Windows 10 upgrade error C1900101

C

cgm5443

Contributor
Joined
Aug 18, 2015
Posts
12
Location
Houston, TX
I was in the middle of posting when my screen went blank. I could not find any of the information I had entered so I'm startng over.

Prior to starting this last attempt to upgrade to Windows 10 I did the following:

1. Cleaned the system of any suspected viruses by running Windows Defender Full System scan.
2. Reboot
3. Complete system scan using Hitman Pro 3.7.9. A number of viruses (malware, Trojans, and suspicious files were found and either removed or quarantined. It took 3 runs, rebooting between each run to completely remove all traces of hostile programs.
4. Reboot
5. Using a command prompt with privileges, I ran "sfc /scannow" which completed without and error. (I captured the details if anybody wants them)
6. Reboot
7. Then I used the DISM package and ran the following:
Step 1. "dism /online /cleanup-image /startcomponentcleanup>"%userprofile%\Desktop\dismclean.txt"


Output from Dismclean.txt =


Deployment Image Servicing and Management tool
Version: 6.3.9600.17031


Image Version: 6.3.9600.17031


The operation completed successfully.


Step 2. Rebooted system to clear any pending flags


Step 3. dism /online /cleanup-image /restorehealth >"%userprofile%\Desktop\restorehealth.txt"


Output from restorehealth.txt=


Deployment Image Servicing and Management tool
Version: 6.3.9600.17031


Image Version: 6.3.9600.17031


The restore operation completed successfully. The component store corruption was repaired.
The operation completed successfully.


Step 4. Going to try and do the "Upgrade to Windows 10 Pro"

Result upgrade failed with error code C1900101

I've about run out of things to try so ANY help would be greatly appreciated
 
Are you now currently running Windows 7?

If so, run sfc /scannow from a CMD screen.
 
If you look at my post, you will see on No. 5 that I did that and that I captured the results. The Scan completed successfully. I'm currently running the Windows 8.1 Pro OS
 
I just noticed that I hadn't fully identified the error C1900101. the full error Id: C1900101-4000D. Sorry for not catching this earlier. Hope it helps because I've been working on this since 08/10/15 and I'm about ready to just stay with 8.1 Pro.
 
I had suggested sfc /scannow to help assure all was still well after the failed upgrade.

Others have successfully upgraded to Windows 10 after uninstalling their a/v & 3rd party firewall.

If you do so, use the removal tool, if applicable - Uninstallers (removal tools) for common Windows antivirus software - ESET Knowledgebase

Here's a thread filled with ideas - https://www.reddit.com/r/Windows10/comments/3f5ivm/why_cant_you_upgrade_to_windows_10_list_your/

I am unaware of the exact meaning of your error code. It's perplexing to say the least.
 
jcgriff2 said:
I had suggested sfc /scannow to help assure all was still well after the failed upgrade.

Others have successfully upgraded to Windows 10 after uninstalling their a/v & 3rd party firewall.

If you do so, use the removal tool, if applicable - Uninstallers (removal tools) for common Windows antivirus software - ESET Knowledgebase

Here's a thread filled with ideas - https://www.reddit.com/r/Windows10/comments/3f5ivm/why_cant_you_upgrade_to_windows_10_list_your/

I am unaware of the exact meaning of your error code. It's perplexing to say the least.
Click to expand...


I do appreciate your suggestions and comments. Whenever I run into a problem like this I have a standard procedure that I use for troubleshooting.
1. I do a "clean boot" (run msconfig-hide all Microsoft services- disable what's left- reboot)
2. Open a command prompt with administrator privileges.
3. Using the command prompt I run procedures that I think will help isolate or clear up the problem ( "sfc, dims, etc" )
4. Where possible I include the following string at the end of the command line. >"%userprofile%\Desktop\name of procedure- date- time.txt".
5. This gives me the output of the cmd in a text file that I can examine and save for future reference.
6. I reboot between each procedure to eliminate pending flags.

Any suggestions for improving my approach to troubleshooting will be greatly appreciated. I'm a 79+ retired test engineer that still enjoys the challenge of learning new ways of doing business

New information: I spent over 5 hours with Microsoft troubleshooting this problem. I gave them access to my system and watched them repeat most of what I had already done. My case has now been elevated to the next level. Microsoft took some information with them to evaluate and will call me on Sunday at 1400 hours CST. I will pass on any information that comes from that

Again thanks for all of your efforts and please keep them coming. Who knows, the next one may be the solution.
Chuck
 
I had been told that I would received a phone call from Microsoft Support Professional between 2PM and 4PM CST on Sunday 8/23/2015. Later I received an email confirming this appointment. I have been waiting since 1:30PM (it is now 7:30PM) and have NOT received the promised call. I've tried to call the number I had been given and have been listening to commercials for the past 1.5 hours. I'm starting to think that I'm being ignored.
 
Microsoft finally called about 1830 hours CST. Again I gave them access to my system and after looking around for about 45 minutes they decided that my current OS was corrupted. After trying a few repairs (which didn't work) I gave permission to rebuilt the system. They started the download of an 8.1 Pro ISO file. Then they hung up on me. About 10 minutes after the download had completed I noticed the cursor starting to move around again (I wasn't touching anything) and realized Microsoft was back. I brought up a text box and asked if I could help and they asked if I remembered where they had put the downloaded ISO file. Being an old test engineer I had written down the storage location and lead them to it. Then they started to reinstall a new Windows 8.1 Pro and left. After the 8.1 pro install had finished I waited for about 1/2 hour. I then decided to do an express setup. I'm not in the middle of installing about 87 updates to the system. Don't know where Microsoft is, tried calling the "special" number I had been given and got a voice recording saying they were "Closed and would reopen in the morning. More later.....
 
Did you ever reestablish contact with Microsoft?

Seems like you were left hanging.

BTW, I agree with your troubleshooting methods, including the capturing of the CMD output -- good idea to do so.
 
Microsoft FINALLY called back at 1500 hours on 8-26-15. He looked over what I had done, then he downloaded a Win 10 ISO file and started another install. Told me that he would hang-up during upgrade and call me back. Upgrade got to 79% total before freezing with a black screen. That was at 1730 hours. At 1900 hours I called Microsoft, got a tier 1 Tech, who checked my reference # and said I was scheduled for a call back, BUT THERE WAS NO TIME FRAME GIVEN. At my request the tech tried to get another level 2 tech to take the case but could not get one. As it currently stands
1. My computer is frozen with a black screen.
2. I'm scheduled to receive a call-back from Microsoft at an Unknown time and Unknown date (I'm "*** u m ing" that it will be 2015)
3. Microsoft may have some specific instructions about what to do immediately after restarting the system so I'm kind of stuck in limbo.

On a positive note, At least I'm talking to REAL PEOPLE not just a machine. Now if I can only learn to understand them.
 
Update: On august 29,2015, I received a "Form Letter" type email from Microsoft stating that they were sorry.... high volume prevented .... would call me within the next 48 hours DURING THE SAME APPROVED TIME FRAME (remember the call when I talk to a Microsoft tech who said I was to receive a call back but there WASN'T ANY TIME FRAME. As it stands now I'm still waiting on a call from Microsoft. Because they have installed a new 8.1 Pro operating system, ran some batch routines to cleanout any residual contaminated files, and checked the system to make sure it was eligible for upgrade, AND it still failed, I think the problem is above my pay grade and I'm at their mercy. After all they did write the software, didn't they?
 
blueelvis said:
Hi cgm5443 ^_^,

Could you please tell us the configuration of your system? Also, please tell us the peripherals attached to the system.

Are you getting a similar message like this?
ubuntu - Why am I getting error C1900101 when I try to upgrade from Windows 7 to Windows 10? - Super User

Please try the solution mentioned there.



-Pranav
Click to expand...

I was asked about my system configuration: Gateway All-in-One, Touch Screen (about 2 points) about 5 years old. It's running windows 8.1 pro upgraded from Windows 7 Ultimate. All internals original. Only items attached were the original keyboard and mouse using the same USB interface device.

I'll be glad to furnish any additional information
 
I finally, WITH HELP FROM ALL OF YOU, got my system upgraded to Windows 10. Following is as complete a list of the steps I took, as best as I can remember. Thanks again for all the help and support. I hope the following helps somebody else.

Steps taken prior to Upgrading to Windows 10

  1. Booted into Bios Setup (because of the speed of the system, I used the boot section of msconfig)
    1. Disabled “Quick Boot”
    2. Disabled “Quiet Boot”
    3. Saved and exited
  2. Opened “Device Manager” and UNINSTALLED the following:
  3. ReadyNAS 104
  4. WDTVLiveoffice (media player)
  5. All printers
  6. All Software devices
  7. Ran sfc /scannow
  8. Saved results of scan into a text file on the desktop for future reference.
  9. Opened a Command Prompt with Admin privilege. The I manually reset the Windows Updates Components using a set of commands that were posted on the Microsoft Community Forum by Annu Singh, a Microsoft Support Engineer. I put the commands into a batch routine in case I needed them more than once. The commands are:


    1. net stop wuauserv
    2. net stop cryptSvc
    3. net stop bits
    4. net stop msiserver
    5. ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
    6. ren C:\Windows\System32\catroot2 Catroot2.old
    7. net start wuauserv
    8. net start cryptSvc
    9. net start bits
    10. net start msiserver
    11. exit (to close command prompt)
  10. Restart computer.
  11. Using the Control Panel, I went into “Windows Update” and restarted Windows 10 upgrade. The upgrade went into the “Black Screen” mode at 71% total and 1% “configuring settings”. After waiting for 3 (timed) hours I performed a pwr off/pwr on reboot. THE UPGRADE STARTED WHERE IT HAD STOPPED and completed the upgrade.


After all of the different attempts by both Microsoft and myself I’m not positive the above steps were the only things that did the trick.

Bottom Line is that Windows 10 is up and running and I’m going through the fine tuning process to arrange things my way.
Thanks for all of the suggestions and support. This has been a great experience for this old man. The world still has a bunch of caring, helpful people.

Chuck
 
Hi Chuck ^_^,

Thank you very much for posting back the solution which worked for you. If I were to take a wild guess, I think that the update proceeded further because you renamed the catroot2 and SoftwareDistribution folders. Both of these folders are the locations where Windows downloads the Updates. So, the set of instructions given by the Microsoft Support Engineer have worked their magic (AFAIK).


Once again, thanks a lot for posting back the solution. I am sure this would help the future visitors :)



-Pranav
 

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

Back
Top