In that case, you can try FileAssassin by Malwarebytes... In my experience, it'll delete anything... And if it fails to delete, you definitely need a disk check with the /f switch... Or just do it from recovery like you mentioned
Not checkdisk, just some learning about how set the ownership/permissions In that specific case is very likely that Intel messed with the permissions, just like Adobe does with its flash player
Guys, for the 10th time, the error was NOT a permissions error, it was that the system was using the files (Files are in use) I had full permissions, I took ownership, hell I could rename, move, cut, paste, I could remove their extensions so they were null files, I could do anything I wanted with them, except delete them Read up on hard linked files Manually deleting Windows.old is simple, done it using nothing but the security tab plenty of times, this was not the problem If it was just a permissions thing, disk clean-up should have succeeded the first time around
Was not in Your case. We already discussed that I'ts very unlikely that here the problem is the same, firstly because the permission is the most common/obvious scenario. Secondly because .sys usually aren't in use if you want you can delete/rename one of them even from the running system w/o any problem