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

Install made with 1.2b is caught in SP1 logon loop

- - - - -

  • Please log in to reply
12 replies to this topic

#1
aaroe

aaroe
  • Member
  • 9 posts
  • Joined 02-August 08
I just got myself together and made a Vista install with the vLite 1.2b.
I did like I normally do and integrated the SP1 with my Vista Ultimate x64 and did some tweaking of it - removing unused languages, drivers etc... nothing critical.

I then continued to install it and everything seemed to work fine - untill the installation process was over and I booted the first time. It began to finish step 3 og 3 of the SP1 process and then continued to reboot. This is then repeated over and over again without me getting any control of the system.

I read about this "logon loop" but also read that the 1.2b should try to prevent it, so I assumed I had been unlucky. I then tried to do the whole vLite process over again in hope of me being a bit more lucky this time - but I wasn't.

Any advice on why this logon loop problem happens and how to avoid it when making a vLite install?

Kind regards
Christian Rasmussen, Denmark.


How to remove advertisement from MSFN

#2
dcatcher

dcatcher

    Newbie

  • Member
  • 15 posts
  • Joined 28-March 08
I happens to get the same problem with server 2008.
After looking for the solution in the forum, I fix it!

It's very simple just delete pending.xml in your winsxs folder, which is in your install.wim file.
You can mount the install.wim file using waik, then delete the file. I don't know other ways.

GL

#3
aaroe

aaroe
  • Member
  • 9 posts
  • Joined 02-August 08
Ok, sounds good that there's a solution for it - but can I make you elaborate on it a bit?

This is my normal procedure for making a vLite install DVD.

1) Copy DVD to HD.
2) Slipstream SP1.
3) Make other tweaks and adjustments.
4) Rebuild.
5) Direct Burn and install.

So if I'm getting what you're saying, there should be file named pending.xml in a folder named winsxs which exists in as part of the data I'll be burning onto the DVD?

So that in order to get it to work correctly, my process of making the vLite install should look like this instead:

1) Copy DVD to HD.
2) Slipstream SP1.
3) Make other tweaks and adjustments.
4) Rebuild.
5) Delete pending.xml file from winsxs folder.
6) Direct Burn and install.

...just to be absolutely sure :)

Thank you for your time.

Kind regards
Christian Rasmussen

#4
dcatcher

dcatcher

    Newbie

  • Member
  • 15 posts
  • Joined 28-March 08

Ok, sounds good that there's a solution for it - but can I make you elaborate on it a bit?

This is my normal procedure for making a vLite install DVD.

1) Copy DVD to HD.
2) Slipstream SP1.
3) Make other tweaks and adjustments.
4) Rebuild.
5) Direct Burn and install.

So if I'm getting what you're saying, there should be file named pending.xml in a folder named winsxs which exists in as part of the data I'll be burning onto the DVD?

So that in order to get it to work correctly, my process of making the vLite install should look like this instead:

1) Copy DVD to HD.
2) Slipstream SP1.
3) Make other tweaks and adjustments.
4) Rebuild.
5) Delete pending.xml file from winsxs folder.
6) Direct Burn and install.

...just to be absolutely sure :)

Thank you for your time.

Kind regards
Christian Rasmussen


I only have the problem when vliting windows server 2008, so no slipstream is involved.
But I think the order you delete pending.xml doesn't matter as long as it's not there. The file seems recording some update operation after reboot.
Just an advice, it's safer to install the vlited system in a virtual machine first, such as virtualbox.

#5
aaroe

aaroe
  • Member
  • 9 posts
  • Joined 02-August 08
Thank you for clarifying :)

The VirtualBox thingy seems very interesting. I had a quick look at it and bu judging on the description of the product, it doesn't seem that I can use it. It seems to be strictly x86 and I'm using a x64 Vista Ultimate :(

#6
oskingen

oskingen

    MSFN Friend

  • Member
  • PipPipPipPip
  • 610 posts
  • Joined 20-January 08
  • OS:none specified
  • Country: Country Flag
it's time for the new RC

#7
Kameleau

Kameleau
  • Member
  • 1 posts
  • Joined 24-April 08

it's time for the new RC


It doesnt work whit the RC.

Splipstream + tweaks and remove things whit Vlite 1.1.6 - OK
Splipstream + tweaks and remove things whit Vlite 1.2 Beta - Logon loop
Tried today Splipstream + tweaks and remove things whit Vlite 1.2RC - Logon Loop

I'm currently retrying splipstream but whitout removing anything just to see...

#8
aaroe

aaroe
  • Member
  • 9 posts
  • Joined 02-August 08

it's time for the new RC


It doesnt work whit the RC.

Splipstream + tweaks and remove things whit Vlite 1.1.6 - OK
Splipstream + tweaks and remove things whit Vlite 1.2 Beta - Logon loop
Tried today Splipstream + tweaks and remove things whit Vlite 1.2RC - Logon Loop

I'm currently retrying splipstream but whitout removing anything just to see...


I can confirm that - tried yet again last night with the new 1.2RC - still hangs on the SP1-installation during the first boot up. Sigh...

#9
aaroe

aaroe
  • Member
  • 9 posts
  • Joined 02-August 08

I happens to get the same problem with server 2008.
After looking for the solution in the forum, I fix it!

It's very simple just delete pending.xml in your winsxs folder, which is in your install.wim file.
You can mount the install.wim file using waik, then delete the file. I don't know other ways.

GL


Dcatcher, could I ask you to explain where this install.wim file is supposed to exist? I can't seem to find it or the winsxs folder anywhere at any stage when working with vLite?

#10
Tomorrow

Tomorrow

    Advanced Member

  • Member
  • PipPipPip
  • 379 posts
  • Joined 20-December 07
  • OS:Windows 7 x64
  • Country: Country Flag

I happens to get the same problem with server 2008.
After looking for the solution in the forum, I fix it!

It's very simple just delete pending.xml in your winsxs folder, which is in your install.wim file.
You can mount the install.wim file using waik, then delete the file. I don't know other ways.

GL


Dcatcher, could I ask you to explain where this install.wim file is supposed to exist? I can't seem to find it or the winsxs folder anywhere at any stage when working with vLite?

In the DVD root menu:Sources\ folder

#11
malibu

malibu

    Newbie

  • Member
  • 11 posts
  • Joined 07-June 06
Even when not integrating service packs or hotfixes during the slipstream process, trying to use windows update after a sucessful install still triggers the loop.

#12
nuhi

nuhi

    nLite & NTLite human.dll

  • Developer
  • 4,400 posts
  • Joined 25-October 03
  • OS:none specified
  • Country: Country Flag
In next version fixed WLAN support removal, it was causing the loop on hotfix install. Please keep it and if it doesn't help attach your preset.
http://www.nliteos.com | http://www.ntlite.com
Remove components and customize Windows

#13
Skraelos

Skraelos

    Newbie

  • Member
  • 11 posts
  • Joined 10-May 07
I'm more than sure it is not about WLAN... I was getting this loop because of Bitlocker Extras integration, and the funny thing it was fixed not by making less removements, but by making MORE removements, I didn't have time to check which one though.. My guess is system restore or event viewer




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users