F5F Stay Refreshed Software Operating Systems Remove DriverStore from Windows.old by deleting it from the recycle bin or uninstalling the old version.

Remove DriverStore from Windows.old by deleting it from the recycle bin or uninstalling the old version.

Remove DriverStore from Windows.old by deleting it from the recycle bin or uninstalling the old version.

Pages (2): Previous 1 2
M
mamaland56
Junior Member
48
12-02-2016, 11:33 AM
#11
The lack of awareness is notable here. Alright, I think I’m finished with you. I wish you’re young and still in that “I know everything” stage. I also hope you leave that phase behind if you plan to work in IT. @ MrMoeJay if you need further help, feel free to ask.
M
mamaland56
12-02-2016, 11:33 AM #11

The lack of awareness is notable here. Alright, I think I’m finished with you. I wish you’re young and still in that “I know everything” stage. I also hope you leave that phase behind if you plan to work in IT. @ MrMoeJay if you need further help, feel free to ask.

K
kingsauron
Member
126
12-02-2016, 07:12 PM
#12
The folder was actually empty, even when hidden and protected files were displayed. I made sure it had no content. It looks like Windows may have crashed during the cleanup, possibly ending the process early, which affected system protection settings. Merging it worked fine for me, but the method you mentioned seems better. It's too late now.
K
kingsauron
12-02-2016, 07:12 PM #12

The folder was actually empty, even when hidden and protected files were displayed. I made sure it had no content. It looks like Windows may have crashed during the cleanup, possibly ending the process early, which affected system protection settings. Merging it worked fine for me, but the method you mentioned seems better. It's too late now.

D
Damianos9011
Junior Member
15
12-03-2016, 02:52 AM
#13
No problem. I appreciate it was empty and that you confirmed. It was the right choice, and I hope you see why I like teaching people the proper way.
D
Damianos9011
12-03-2016, 02:52 AM #13

No problem. I appreciate it was empty and that you confirmed. It was the right choice, and I hope you see why I like teaching people the proper way.

T
TheLapisOzalot
Junior Member
5
12-03-2016, 04:30 AM
#14
Just jelly and in my nerd phase. Eventually I grew up.
T
TheLapisOzalot
12-03-2016, 04:30 AM #14

Just jelly and in my nerd phase. Eventually I grew up.

J
jellybeansean
Member
164
12-03-2016, 10:32 AM
#15
It seems the message is unclear and may not convey a clear intent. I aim to provide accurate guidance while addressing any confusion. Let me know how you'd like to proceed.
J
jellybeansean
12-03-2016, 10:32 AM #15

It seems the message is unclear and may not convey a clear intent. I aim to provide accurate guidance while addressing any confusion. Let me know how you'd like to proceed.

M
marcavrelius
Member
60
12-04-2016, 06:05 PM
#16
The problem stems from access rights. The earlier Windows version likely had a different identity for administrator accounts. The quickest fix is to open the properties of the windows.old directory, set the owner to your personal account (requires admin privileges), and then enforce inheritance on all subfolders. After that, just press delete. This approach seems straightforward, though it might not be ideal. Here are some reasons behind it: 1. Windows updates: previous update installers now reside in the WinSxS folder, which can interfere with newer versions. If you've been using this setup for a while, especially since Vista, you may have accumulated many updates. 2. The driver store (C:\Windows\SysWOW64\DriverStore) will now hold all your outdated drivers, potentially causing conflicts because Windows will try to use the XP or Vista driver when searching online instead of checking current sources. There are additional factors mentioned by dalekphalm, but it appears you might not be fully aware of the risks involved.
M
marcavrelius
12-04-2016, 06:05 PM #16

The problem stems from access rights. The earlier Windows version likely had a different identity for administrator accounts. The quickest fix is to open the properties of the windows.old directory, set the owner to your personal account (requires admin privileges), and then enforce inheritance on all subfolders. After that, just press delete. This approach seems straightforward, though it might not be ideal. Here are some reasons behind it: 1. Windows updates: previous update installers now reside in the WinSxS folder, which can interfere with newer versions. If you've been using this setup for a while, especially since Vista, you may have accumulated many updates. 2. The driver store (C:\Windows\SysWOW64\DriverStore) will now hold all your outdated drivers, potentially causing conflicts because Windows will try to use the XP or Vista driver when searching online instead of checking current sources. There are additional factors mentioned by dalekphalm, but it appears you might not be fully aware of the risks involved.

M
Maakuzw
Junior Member
32
12-05-2016, 12:44 AM
#17
This involves a permission problem. Only SYSTEM has the ability to remove the file. The thread is outdated but useful if you need help: sign in with admin privileges, right-click the Windows.old folder, select Properties, go to Security tab, click Advanced, choose "Change" for Owner (currently SYSTEM), enter your admin account name, confirm by checking the box, then click OK. After that, check the box for replacing owner on subcontainers and objects, apply, and finally replace all child object permissions and apply again. If you skip the first step before the second, you'll get an access denied message.
M
Maakuzw
12-05-2016, 12:44 AM #17

This involves a permission problem. Only SYSTEM has the ability to remove the file. The thread is outdated but useful if you need help: sign in with admin privileges, right-click the Windows.old folder, select Properties, go to Security tab, click Advanced, choose "Change" for Owner (currently SYSTEM), enter your admin account name, confirm by checking the box, then click OK. After that, check the box for replacing owner on subcontainers and objects, apply, and finally replace all child object permissions and apply again. If you skip the first step before the second, you'll get an access denied message.

K
Krunchy53
Junior Member
3
12-14-2016, 01:33 PM
#18
It could be the fastest solution, yet it's quite far from the optimal choice. I hoped for a method to challenge this impulsive sharing.
K
Krunchy53
12-14-2016, 01:33 PM #18

It could be the fastest solution, yet it's quite far from the optimal choice. I hoped for a method to challenge this impulsive sharing.

Pages (2): Previous 1 2