Features regression bug? (Win7)

P

pmikep

Active Member
As in my previous post, I'm trying v1.5.0.5840 on Windows 7 SP1 iso.

The last time I seriously used NTLite was in May. At the time, I was experimenting with getting WMC to work. At that time, NTLite's Features Removal was breaking Windows 7. But then I tried a quick September build and I recall posting (In the old forum?) that Features was fixed.

(1.4.0.5537 stable, per my post on September 4. See https://www.ntlite.com/forum/discussion/comment/8198/#Comment_8198 )

But now it seems broken again. (I noticed someone complaining about it for a Win10 build, saying he had to leave fax and internetprintingclient enabled.)

https://www.ntlite.com/community/index.php?threads/another-features-problem-i-am-facing.82/#post-708

So, to begin, I first made a new vanilla base iso with just the Convenience Rollup using 5840.

I took that and used NTLite to do some major surgery on that iso.

I took out the two XPS items in Features Removal. I left in IE8.

When I tried to remove IE8 in the running Windows 7, I got our old message that "An error has occurred. Not all of the features were successfully changed."

Rats.

Preset attached.
 
Last edited:
Agreed on the last part. My Win7 desktop runs fine with my "psueo-extreme" removals prior to install, even tho sfc /scannow is not perfect.
 
So I took a quick look at the CBS.log on my friend's computer after doing the sfc /scannow. If I'm reading it right, it might have repaired some old /NET Framework files that I probably removed a year ago.

I'm developing a hypothesis that one reason that Windows can repair corrupted files easier when Removals are done after installation (instead of before) is because the wsus winsxs older is intact. (Updated per Clanger.)

Which brings up a question: If I use NTLite Live on a running Win7 to remove some stuff, and then run sfc /scannow, does sfc put the stuff back in to Windows that I just removed?

@nuhi?
 
Last edited:
I take it you mean the winsxs folder is intact? SFC would look for a replacement good file in winsxs and copy it over, providing you have not removed Windows Component Store(WinSxS). In the old days with xp you had to insert your install media for a good copy for sfc.

If i am correct any removal with ntlite will also remove X components files from winsxs so even if you run sfc it cannot replace anything it sees as corrupted because those files no longer exist in winsxs. I see System File Checker(SFC) is removable and has a Recommended Compatibility Option. If it was absolutely necessary then it would be super locked by Protections or not even be an option.
 
I corrected my post above. (Thanks.)

"If i am correct any removal with ntlite will also remove X components files from winsxs so even if you run sfc it cannot replace anything it sees as corrupted because those files no longer exist in winsxs." That sounds right. Waiting confirmation from nuhi. (Or is that "awaiting confirmation ..."?)
 
Last edited:
What i would suggest is if sfc reports a file as corrupt, find a known good copy and compare file hashes, if they match, sfc is wrong. You could run CHKDSK after sfc complains, then run sfc again and see what it says.
 
Thanks Mike, will group all the Win7 Features config reports and dedicate some time to it these days, should be simple enough to fix.
 
You must log in or register to reply here.
Back
Top