Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Windows could not configure one or more system components..


  • Please log in to reply
9 replies to this topic

#1
Kahenraz

Kahenraz
  • Member
  • 8 posts
  • Joined 18-December 14
  • OS:none specified
  • Country: Country Flag

I am attempting to build an updated ISO of Windows 7 SP1 x64. I am using the "Windows 7 Professional SP1 Media Refesh x64" iso as a base with the following updates slipstreamed with WinToolkit 1.5.3.5:

 

http://pastebin.com/raw.php?i=ZUZ4gdeD

 

These updates were obtained through Alphawaves' Downloader which is built into WinToolkit.

 

Upon installation on a VMWare image, I receive the following error:

 

 

 

Windows could not configure one or more system components. To install Windows, restart the computer and then restart the installation.

 

I only receive this error after building a slipstreamed disc. I would attempt to narrow down which update is causing the problem but considering it takes over three hours to integrate all of these updates, is very challenging.

 

Can anyone provide some insight on this?


Edited by Kahenraz, 20 December 2014 - 06:36 AM.



How to remove advertisement from MSFN

#2
Kahenraz

Kahenraz
  • Member
  • 8 posts
  • Joined 18-December 14
  • OS:none specified
  • Country: Country Flag

Still trying to narrow this down. The problem seems to be one of these:

 

Windows6.1-KB2524840-x64.msu
Windows6.1-KB2525835-x64.msu
Windows6.1-KB2526629-v3-x64.msu
Windows6.1-KB2529781-x64.msu
Windows6.1-KB2529825-x64.msu
Windows6.1-KB2533552-x64.msu
Windows6.1-KB2533623-x64.msu
Windows6.1-KB2535094-x64.msu
Windows6.1-KB2535158-x64.msu
Windows6.1-KB2537203-x64.msu
Windows6.1-KB2538047-x64.msu
Windows6.1-KB2539513-x64.msu
Windows6.1-KB2545561-x64.msu
Windows6.1-KB2545698-x64.msu
Windows6.1-KB2545735-x64.msu
Windows6.1-KB2546868-x64.msu
Windows6.1-KB2547666-x64.msu
Windows6.1-KB2549067-v2-x64.msu
Windows6.1-KB2549079-x64.msu
Windows6.1-KB2550648-v2-x64.msu
Windows6.1-KB2551090-v2-x64.msu
Windows6.1-KB2551687-x64.msu
Windows6.1-KB2554231-x64.msu
Windows6.1-KB2554859-x64.msu
Windows6.1-KB2554876-v2-x64.msu
Windows6.1-KB2555189-x64.msu
Windows6.1-KB2555392-x64.msu
Windows6.1-KB2555948-x64.msu
Windows6.1-KB2559392-x64.msu
Windows6.1-KB2560289-x64.msu
Windows6.1-KB2560656-x64.msu
Windows6.1-KB2564958-x64.msu
Windows6.1-KB2566314-x64.msu
Windows6.1-KB2570947-x64.msu
Windows6.1-KB2574819-v2-x64.msu
Windows6.1-KB2575866-x64.msu
Windows6.1-KB2575928-x64.msu
Windows6.1-KB2577968-x64.msu
Windows6.1-KB2578214-x64.msu
Windows6.1-KB2579686-x64.msu
Windows6.1-KB2581608-x64.msu
Windows6.1-KB2581690-x64.msu
Windows6.1-KB2582679-x64.msu
Windows6.1-KB2584475-x64.msu
Windows6.1-KB2584577-x64.msu
Windows6.1-KB2589154-x64.msu
Windows6.1-KB2591271-v2-x64.msu
Windows6.1-KB2591500-v3-x64.msu
Windows6.1-KB2591857-x64.msu
Windows6.1-KB2592687-x64.msu
Windows6.1-KB2594586-x64.msu
Windows6.1-KB2598845-x64.msu
Windows6.1-KB2600100-x64.msu
Windows6.1-KB2603203-x64.msu
Windows6.1-KB2603229-x64.msu
Windows6.1-KB2604115-x64.msu
Windows6.1-KB2607047-x64.msu
Windows6.1-KB2614892-x64.msu
Windows6.1-KB2615327-x64.msu
Windows6.1-KB2616386-x64.msu
Windows6.1-KB2616879-x64.msu
Windows6.1-KB2618301-x64.msu
Windows6.1-KB2618535-x64.msu
Windows6.1-KB2618640-x64.msu
Windows6.1-KB2618752-x64.msu
Windows6.1-KB2619082-x64.msu
Windows6.1-KB2619260-v2-x64.msu


#3
bphlpt

bphlpt

    MSFN Addict

  • Member
  • PipPipPipPipPipPipPip
  • 1,915 posts
  • Joined 12-May 07
  • OS:none specified
  • Country: Country Flag

A way to narrow the list down would be to split the list in half.  Try to integrate just the first half.  If no errors, repeat the integration on the same initial source with only the second half of the list.  Once you have determined which half of the list has the problem continue the experiment in the same way by splitting the "bad" half in half again.  It will be very boring time consuming work, but it should allow you to find the problem.

 

Cheers and Regards


Posted Image


#4
Kahenraz

Kahenraz
  • Member
  • 8 posts
  • Joined 18-December 14
  • OS:none specified
  • Country: Country Flag

Yes, that's what I'm doing.  :zzz:



#5
Kahenraz

Kahenraz
  • Member
  • 8 posts
  • Joined 18-December 14
  • OS:none specified
  • Country: Country Flag

While narrowing this down and installing updates slowly, the problem was avoided. Adding all of the updates at once to a clean SP1 disc still causes this issue.  :huh:



#6
Kahenraz

Kahenraz
  • Member
  • 8 posts
  • Joined 18-December 14
  • OS:none specified
  • Country: Country Flag

The issue appears to be related to attempting to integrate Desktop Protocol 8.1 and its associated prerequisites and updates.

 

The KBs are:

 

Windows6.1-KB2574819-v2-x64.msu
Windows6.1-KB2857650-x64.msu
Windows6.1-KB2592687-x64.msu
Windows6.1-KB2830477-x64.msu
Windows6.1-KB2913751-x64.msu
Windows6.1-KB2923545-x64.msu
Windows6.1-KB2984976-x64.msu
Windows6.1-KB3005781-x64.msu

  • Tripredacus likes this

#7
PinkFreud

PinkFreud

    Member

  • Member
  • PipPip
  • 100 posts
  • Joined 12-August 10
  • OS:Windows 7 x64
  • Country: Country Flag

 

The issue appears to be related to attempting to integrate Desktop Protocol 8.1 and its associated prerequisites and updates.

 

The KBs are:

 

Windows6.1-KB2574819-v2-x64.msu
Windows6.1-KB2857650-x64.msu
Windows6.1-KB2592687-x64.msu
Windows6.1-KB2830477-x64.msu
Windows6.1-KB2913751-x64.msu
Windows6.1-KB2923545-x64.msu
Windows6.1-KB2984976-x64.msu
Windows6.1-KB3005781-x64.msu

 

 

KB3005781 is not a prerequisite for RDP 8.1 https://support.micr...1?wa=wsignin1.0

KB2913751 is superseded by KB2994023

 

[attachment=39033:supersede.PNG]

 

HTH :)


Edited by PinkFreud, 03 January 2015 - 06:22 PM.


#8
drtweakllc

drtweakllc
  • Member
  • 2 posts
  • Joined 19-February 15
  • OS:Windows 7 x64
  • Country: Country Flag

I'm having the exact same issue, I have made about 10-15 setup USB drives and cannot narrow down the update causing the issue. Does anyone have a list of know updates that can cause issues when slipstreaming?



#9
maxXPsoft

maxXPsoft

    MSFN Master

  • Developer
  • 2,890 posts
  • Joined 14-November 03
  • OS:Windows 7 x64
  • Country: Country Flag

I'm having the exact same issue, I have made about 10-15 setup USB drives and cannot narrow down the update causing the issue. Does anyone have a list of know updates that can cause issues when slipstreaming?

 

These are the ones won't inject for me, I put all in one folder and watch the command output and if one fails you can see it real easy

Your mileage may vary but these are known fails for me

[No_Inject]
List=971033,2506143,2533552,2607047,2647753,2791765,2809215,2809900,2823180,2835174,2912390,2917500


Download ++> Windows 7 + 8 Unattended DVD + App Installer + Services Disabler + Load All Button + XML Creator
Jump2Reg - Registry: - Oct 4, 2013 - Version 3.0.4 - 98, ME, NT, 2K, XP, VISTA, Seven, Windows 8+ and 32 or 64 bit

XP Unattended CD/DVD creator - Version 4.1.7
Sample xml + Setupcomplete + Add Right click .wim Windows 7 or Windows 8/8.1

#10
drtweakllc

drtweakllc
  • Member
  • 2 posts
  • Joined 19-February 15
  • OS:Windows 7 x64
  • Country: Country Flag

Figured it out, there are many updates that require .NET Framework 4.5. You can slipstream it into your disc, the download link is here .NET Framework 4.5 and if you are using WinToolkit 1.5.3.12 add it under "add-ons". Once done everything works fine and the error is gone.

 

maxXPsoft, thank you for your input.

 

:yes:






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users