Jody Thornton

Well I wouldn't be able to answer that because I sign into Windows 8 using a local account, not a Microsoft one (and if I'm not mistaken, such an issue wouldn't affect Vista or XP)

Oh OK. I'm simplifying the process a lot, so this is how I understand it: Let's say the component "shell32.dll" is initially released in October 2012. There are three updates for colour rendering problems, and two for security holes (I'm making this up of course ...lol). The way Windows 8 removes components, is that it keeps the original version, the newest colour-fixed one, and the newest security-fixed one. Then Windows 8 uses hardlinks to point to the correctly matched version to support whatever program you run. In the Windows 8.1 /resetbase option will remove all but the newest version, and JUST use that. I hope I have that correct. It appears that DISM++ calculates that (if I were able to use /resetbase) I could rid of an additional 1.46 GB.

It does. It sets the currently installed components as the new "base" components, and removes everything else. The Start Component Cleanup command will delete older updates but not replace older components that came with the system initially that have been replaced. Thanks for helping me though.

Hey Folks: On Windows 8.1, there is the /resetbase switch that was designed to remove all older replaced components in the WinSxS folder. Windows 8 cannot do this. Now I tried DISM++ (sorta like Ccleaner) which can do this for the component store, but only if you have Windows 8.1 or higher. Does anyone know of a tool or method that CAN reset the base components to the latest installed? on Windows 8?

Oh I have no problem with that. Jaclaz's comment were very complete mind you. And I suppose I'd have more to say, but yes in a thoughtful manner.

When I wanted to change mine, I just put in a PM to xper (pretty sure it was xper) and they got 'er done.

And I respect that. Again, no ill will meant. But I think being able to disagree (and to express why) is a good thing too. Anyway, no more on this from me, I promise.

Yes, I know accountability can be equated to corporate blame. Still you want to be able to pick up a phone a call your vendor right? I do have to ask something though (and this isn't starting a fight - just hear me out). Why is my negativity expressed towards XP frowned upon, yet we have ENTIRE threads called "Windows 10 is the worst crap ever"? Now I agree, I hate Windows 10 too, but Dibya would have you believe that even Windows 7 and 8 have "crap-wares" submitting info to the government. But me expressing that XP in a corporate environment is ..... er, a bad idea? See what I mean? I really think we should be able to openly discuss, argue (politely) and even disagree with our points and beliefs. No personal vendetta is ever meant. If there is real offense taken, then we are taking this all too seriously. I find I learn best when sides disagree, because you hear other points of view. When we all agree, nothing new is exchanged, right?

Interestingly, the update for v4.7 installed, even though I only have .NET v4.5 that came with Windows 8. Hmmmmmmmmmmmmmm...

Hooray!

Just checking in to see how things went for September. I'll be updating Windows 8 tomorrow morning.

I knew I forgot something today. I'll get at it tomorrow morning - updates that is

Done a month ago

I meant it more as "If a company has to bear liability for something going wrong, and IT systems have something to do with that, then shouldn't supported systems be always in use?" - that's what I meant. I don't always believe that discourse on a thread should have to be agreeable at all times. If I really think XP being used in a business is bad, and this thread "celebrates" it, should I not be able to express disagreement? I never want to just be someone who goes along with the tide of popular opinion. That's just being disingenuous. Anyway, I will leave it at that. I understand what you're trying to prevent. No harm intended.

[Thread split from a previous one] So? You're just pointing out departments where IT personnel should be fired for running behind ...lol. I'm OK for running XP when NOTHING connects to it (like my music system - but I only use it because the computer was already set up and working. I would never do it again). But professional environments that are liable in any way should use supported software.

Glad to hear RetroZilla may be a going concern again

But just because support has ended, doesn't mean copyright has expired. In fact, copyright statues are what allow Microsoft to do what it wishes with XP. Remember, it's their product, not ours. So if they had the technology to zap it from your machine and disallow you to run it, that should be legal, because they get to dictate HOW you use their product. You only use it under license. You never "own" a copy, or "own" the OS. So it matters none what patches are or aren't released and on what, and repeat whatever about WEPOS and SMB and blah blah - none of that matters at all.

I thought it meant "For Practical Purposes" but I guess I'm wrong eh?

I wasn't trying to start a fight. But copyright for XP still exists. By no means is it abandonware. If I install XP today then I still have to activate it.

But is it legal to use? (I'm guessing activation is bypassed right?)

Touche! You got me there

Are those blocked ads I see?

Not really. I was just curious that the updates install, WITHOUT me installing v4.61. I found a page recommending to install them on systems with v4.5 and v4.52. Oh well.

I just got through all of my updates. I find it odd that, Even though I only have .NET v4.5 installed with Windows 8, that v4.61 updates seem to install without complaint. If I don't want to upgrade to .NET v4.61, should I install those updates? Nice that the forum upgrade has reduced the spacing between the lines to a sane level again. (Thanks Xper)

It's kinda like how the Windows XP Forums here at xpforums.com cater to an old OS, however they recently had to upgrade to new forum software, which puts it out of the reach of many compatible browsers. I hear ya! Imagine if I were putting out a podcast about "getting back to simplicity and life - and telling people how to get out more and leave the PC and smartphone behind" ... but guess what? You still need a computer to listen