what if I come back ?

Most of the files you see inside the windows directory aren't plain files, are just hardlinks to the SxS directory, so (still guessing) some small mess at the FS level can explain that.

Just download the hard link shell extension to understand graphically how they works.

That's a matter pretty clear for *nix people but completely obscure to most of the windows users given there is no trace of them on windows explorer.

 

That would begin to make more sense then, renaming and moving the 'links' wouldn't remove their association with the files that actually are in use in SxS then I'm guessing

So for future reference, is there a way to unlink them, if that is actually what was going on?

 

Install the hard link extension. You will see all the hard links that points to a file on the property tab.

It's a pretty hand tool, say to move the cache of a browser on a ramdisk w/o changing anything on registry or browser's config files, and similar cases

It's something that should be included by default by MS, at least since the days of XP.

A filemanager that doesn't know filesystem's capabilities is a toy not a filemanager.

 

Yea agreed, might have saved me two days of headache

Thanks for the info

EDIT - Right, now I see the links, never knew that, I always thought they were standalone files

I don't see any way to unlink them with that extension though, which seems to have been the issue with removing them from windows.old

-

I'm guessing that the problem is that the links dir location is not changed to C:\Windows.old\WinSxS, during the upgrade and remains just C:\Windows\WinSxS, which means the link is now valid for the new install causing problems deleting it

Question is now, how to edit that link to disconnect it from the current install?

 

Red ones are hard links, no need to unlink. Practically it's one file mapped N times on the file allocation table (there isn't a "master and a slave"), so (normally) you can create a new link trough the extension, and you can delete the link, just like a normal file.

But, if you rename one hard link the name of the hard link changes while the link survives. So my point was to see the other file eventually still linked to your renamed file.

Maybe windows still looked at the original one even if you renamed one of its links. I repeat just a guess, but seem reasonable.

 

You need to login to view this posts content.

 

Indeed normally there isn't any problem (aside the permissions) deleting it.

That's why I suspected that when the installation moved windows to windows.old messed/crossed some links between windows and windows.old. That's what I mean. Not sure if it's right given I never faced that problem.

 

Yea that's what I think has happened, it failed to add the Windows.old part of the link, so was now valid for the current install

Trying to find commands to break the links, doesn't seem to be very easy

 

how much cost a hdd or ssd these days ?
[ or maybe you already have a spare hdd / ssd ]

why you don't keep your 10586 intact on your actual hdd/ssd
and use another media for 14332 ?

if you have already the entitlement
will be available on both installs

c

 

You need to login to view this posts content.

 

You're activated with the generic key 3V66T, so that means it's activated with something called a "Digital Entitlement". Your hardware nfo is stored on M$ servers so You don't use your Old key anymore. Basically as long as You don't change the Motherboard You can reinstall Windows 10 over and over and never enter a Key.

 

Thanks
What about going again to the "insider program" and try another new version I will be always activated..?? any recommendations...??

 

i think im gona buy an oem pro key for 29 in case mobo breaks past july 29.. before they go up in price

 

Thanks...
I suppose I'll get one of those keys on "windows store" isn't..??

 

i bought game keys with not a single problem at kinguin.net. they got pro too