Windows in "Component Configuration Mode"?

pmikep

Active Member
Saw a post by Clanger about slimming down winsxs so thought I would try it. (Thanks, Clanger. Didn't see that option before. Will probably remove only duplicates to be safe.)

Got this message when I loaded my host live.

strange warning.jpg

Never seen it before. What does it mean?

I didn't try rebooting to see if cleared. (FWIW, am running quite a lot of stuff right now, including two VM's, and two apps in Comodo's Sandbox.)

I had just run diskcleanup the other day to remove some old KB update archives. Haven't rebooted since cleaning those out either. (Who wants to reboot in the middle of work?)

1.7.0.6440.
 
Last edited:

Clanger

Well-Known Member
I see that when i run ntlite after doing a dism removal on a running w7 system, something is pending and no matter how many times i rebooted ntlite always complains. Because dism isnt as functional as it is on windows 10 it is very hard/nigh on impossible to fix it. I had to go into the registry and delete entries to clear it and ntlite to be happy to run. :)
 

pmikep

Active Member
Thanks for the quick reply.

Per my OP, first time I've seen it. If it doesn't clear after a reboot (later someday), then I'll ask you what keys I should delete in the Registry.
 

Clanger

Well-Known Member
It will be because you need to reboot after an update or have configured a Feature. Multiple reboots doesnt clear it, pending gets stuck.

If you get stuck, holler.

I would be careful about cleaning out winsxs in Components, especially if you need a fully featured system. I can because of my needs and its an easy way to gain 1gb+ without breaking much and bricking w10.

Ive always been a tinkerer.
 
Last edited:

Clanger

Well-Known Member
pmikep You are a few hours behind me here so im going to post this now just in case its needed. It may help other w7 users with the same problem.

This worked for me on w7 sp1(untouched) x64 after 1 package removal then a live ntlite removal. This shouldnt be needed on w10 because it has better dism functionality.
This may seem silly but i am not going to recommend it, bricking my pc is 1 thing, bricking someone elses due to bad information is another thing. I would wait for Nuhi or abbodi to give their opinions 1st.

You are going to need to run regedit with elevated privililedges and you will need Sordums PowerRun.
Lauch PowerRun and click regedit. Go to the following key
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\SessionsPending
Capture.PNG
Delete those subfolder entries one by on. Exit regedit.

Not sure about this part because it was quite a while ago. Search your C: drive, you have raid dont you? Look for a file called Pending.xml. You may have to Take Ownership of it to delete it. Restart.
Launch NTLite, do what you need to do. NTLite will soon moan if it didnt work.

It worked for me but i would like to hear an expert opinion though.
 
Last edited:

pmikep

Active Member
I searched for pending.xml and sure enough, it's there. (Along with older versions of same. ) It is dated yesterday, which is when I ran disk cleanup and removed the old archive KB's. So I'll try rebooting later tonight and see if that clears things up.

Always learning something new. (nuhi should write a book about Windows.)
 

Clanger

Well-Known Member
C:\Windows\servicing\Sessions - delete everything except Sessions, this is the latest one.
 

pmikep

Active Member
Good news. I rebooted Windows and sure enough, it did it's "Updating Components" thing on shut down.

Apparently Windows needs to delete some links to the now removed KB archive files, and can't do that until shutdown. (Windows should probably warn you that a reboot will be needed to complete the clean up operation.)

Anyway, on reboot, NTLite loaded my Live image fine and, thanks to Clanger, I found the "hidden" check mark where I could remove duplicate winsxs stuff.

(Hidden in the sense that "Window Components Database" was grayed out, as though I had no choice about its children. nuhi is this intended behavior or a GUI 'bug'?) But when I drilled down in the child list, I found that the check mark next to duplicates was solid black and white. So I unchecked it.

I'm not sure how much "space" I saved (since winsxs uses phantom space). But it sure looks prettier in SpaceMonger's display of used space for Windows.
 
Last edited:

Clanger

Well-Known Member
I have just run these live, Explorer reports winsxs as 5.02gb and 5.09gb size on dsic. Removed files 1779mb.
Nuhi did tell me a way to accurately tell winsxs size but it was ages ago.

manifestbackup 'Manifest Backup (WinSxS\Backup)'</c>
manifests 'Windows Component Database'</c>
optionalfeatures 'Optional Features'</c>
sfc 'System File Check (SFC)'</c>
tempcache 'Cache and temp files'</c>
windowsupdate 'Windows Update'</c>
winsxs 'Windows Component Store (WinSxS)'</c>

Ive got protections disabled in settings so everything was removable
 

Clanger

Well-Known Member
Exactly which component do you mean? Ive already got the winsxs backup and update cleanup compatible in my presets.
 

pmikep

Active Member
It was the Backup. I must have missed it in your Preset. Or perhaps it's a relatively new feature in NTLite?

It probably works better in Live and I don't use Presets in Live. I shoot from the hip to do simple clean up stuff Live.

I want to add that my latest refreshed Lited Win7 is working very well. Thanks, nuhi!
 

Clanger

Well-Known Member
Try setting .net services to manual so they only run when you need them too.

I usually use an ini file with ccleaner to clean out extra muck but i dont know exactly what ntlite cleans up, would be handy toknow and combine the 2 if needed.
 

pmikep

Active Member
Now that you mention it, I do recall seeing the item in the xml. I'll have to check my GOLD preset to see if I had it when I did my refresh.

Even I did, it's possible that winsxs grew since refresh.

Anyway, I learned to specifically look now to make sure that winsxs backup is removed.
 

Clanger

Well-Known Member
Im just running a test now, ltsb lite with winsxs totally stripped out.

Once you are experienced then disable all protections so you caan access everything, it all helps, more so on w10.
 

pmikep

Active Member
You were correct - <c>manifestbackup "manifest Backup (winSxS\backup)" </c> is in my last off-line Preset.

Probably got it from your Preset.

Thanks!
 
Last edited:

Clanger

Well-Known Member
You were correct - <c>manifestbackup "manifest Backup (winSxS\badkup)" </c>
If you got that line copied from a preset is report it, typo. SXS backup isnt so much a component, its a cleanup and free(wont break nothing) cleanup.
 

pmikep

Active Member
It was a typo on my part. Comodo 11 won't let me cut & paste to my sandboxed browser. (Yet. It's supposed to allow it in an upcoming update.)
 

nuhi

NTLite developer
Staff member
pmikep, thanks for the feedback.
NTLite detects pending live changes and warns a user to reboot, so that worked as expected.
True, Windows should say the same instead of juggling with tons of pending data. But since it works, kudos for them on the will to reduce reboots.

Grayed out base component is disabled as it's protected by Compatibilities, but then it confused you to not expand it.
Hm, currently I don't see any other way, just click on any plus, even if the base component is protected.
 
Top