Compelling reading as question in Hardware. Window's 10 related.
-
I have a box with many large-capacity harddrives and I'm running Windows 10 (I might be from the future and I'm getting a message from myself telling me that Windows 10 is now passe; what are ya going to do, right?). At least three of my large-capacity drives are HIDDEN, meaning that no drive letter is currently assigned to them. All drives on the system show up in Device Manager, even the ones that are only partition stubbs and have never held any data or user-accessible content. The reason for putting these drives behind the scenes is many fold (ha, "manifold"). The main reason being that the content kept on them is redundant. Which leads me to my question: When Windows, in general, begins it's reign of supremacy over my UPDATE/UPGRADE schedule, by background loading/downloading/installing then insisting (on whatever final action is necessary to some degree) on displaying the green checkmark, is "it" capable or does it "actually" take a look at those drives that Windows Explorer CAN NOT see (the aforementioned hidden members) to describe some system state and/or take note of drive space on them ... before it begins this tirade of going through the download/install update? So, I guess I'm also asking whether anyone has ever encountered Windows sacking disc-space on a drive they've deemed non-accessible just for this non-documented behavioral annoyance?
-
I have a box with many large-capacity harddrives and I'm running Windows 10 (I might be from the future and I'm getting a message from myself telling me that Windows 10 is now passe; what are ya going to do, right?). At least three of my large-capacity drives are HIDDEN, meaning that no drive letter is currently assigned to them. All drives on the system show up in Device Manager, even the ones that are only partition stubbs and have never held any data or user-accessible content. The reason for putting these drives behind the scenes is many fold (ha, "manifold"). The main reason being that the content kept on them is redundant. Which leads me to my question: When Windows, in general, begins it's reign of supremacy over my UPDATE/UPGRADE schedule, by background loading/downloading/installing then insisting (on whatever final action is necessary to some degree) on displaying the green checkmark, is "it" capable or does it "actually" take a look at those drives that Windows Explorer CAN NOT see (the aforementioned hidden members) to describe some system state and/or take note of drive space on them ... before it begins this tirade of going through the download/install update? So, I guess I'm also asking whether anyone has ever encountered Windows sacking disc-space on a drive they've deemed non-accessible just for this non-documented behavioral annoyance?
I'm pretty sure it caches the updates on the C drive, and if the C drive doesn't have enough space, it throws an error. I don't believe it starts looking for available space on other drives.
The difficult we do right away... ...the impossible takes slightly longer.
