{"id":5810,"date":"2022-07-05T03:27:11","date_gmt":"2022-07-05T03:27:11","guid":{"rendered":"https:\/\/pariswells.com\/blog\/?p=5810"},"modified":"2022-07-05T03:27:11","modified_gmt":"2022-07-05T03:27:11","slug":"reserved-names-in-paths","status":"publish","type":"post","link":"https:\/\/pariswells.com\/blog\/research\/reserved-names-in-paths","title":{"rendered":"Reserved Names in Paths"},"content":{"rendered":"

Windows has several rules around naming files\/folders\/paths<\/p>

https:\/\/docs.microsoft.com\/en-us\/windows\/win32\/fileio\/naming-a-file<\/p>

One of these that I run into often enough to remember it\u2019s a thing but not how to fix it is reserved names in paths CON, PRN, AUX, NUL, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, and LPT9.<\/p>

Also avoid these names followed immediately by an extension; for example, NUL.txt is not recommended.<\/p>

For more information, see Namespaces. You can\u2019t rename the file using file explorer, cmd, powershell or anything else. The only way to do it was to call a specific API with powershell. Note this also requires the literal path prefix of \\\\?<\/p>

[System.IO.File]::Move([file:\/\/C:\/con.ucf]\\\\?\\C:\\con.ucf,”C:\\co2n.ucf”)<\/p>","protected":false},"excerpt":{"rendered":"

Windows has several rules around naming files\/folders\/pathshttps:\/\/docs.microsoft.com\/en-us\/windows\/win32\/fileio\/naming-a-fileOne of these that I run into often enough to remember it\u2019s a thing but not how to fix it is […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-5810","post","type-post","status-publish","format-standard","hentry","category-research"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t