- Joined
- Aug 21, 2015
- Messages
- 1,667 (0.53/day)
- Location
- North Dakota
System Name | Office |
---|---|
Processor | Ryzen 5600G |
Motherboard | ASUS B450M-A II |
Cooling | be quiet! Shadow Rock LP |
Memory | 16GB Patriot Viper Steel DDR4-3200 |
Video Card(s) | Gigabyte RX 5600 XT |
Storage | PNY CS1030 250GB, Crucial MX500 2TB |
Display(s) | Dell S2719DGF |
Case | Fractal Define 7 Compact |
Power Supply | EVGA 550 G3 |
Mouse | Logitech M705 Marthon |
Keyboard | Logitech G410 |
Software | Windows 10 Pro 22H2 |
So I robocopy-ed a directory the other day, and realized partway through the operation that I'd screwed up. Ctrl-C, time to delete the directory and start over. But it's not there. At least, not according to File Explorer or dir. I can type the path and get there, and dir then shows the contents, but it won't let me delete a bunch of the files. Spend a few minutes reading up on Powershell file manipulation commands, then think to myself, "I wonder if Windirstat will see it?" Sure 'nuff, pops right up. Not only that, but it deletes the whole thing without a peep of complaint. rmdir was much less accommodating. By which I mean spit out a couple of dozen errors about permissions. Suppose there was some flag set or not set that caused the MS commands to freak out, but Windirstat doesn't care about. Or something.