Instal Steam
login
|
bahasa
简体中文 (Tionghoa Sederhana)
繁體中文 (Tionghoa Tradisional)
日本語 (Bahasa Jepang)
한국어 (Bahasa Korea)
ไทย (Bahasa Thai)
Български (Bahasa Bulgaria)
Čeština (Bahasa Ceko)
Dansk (Bahasa Denmark)
Deutsch (Bahasa Jerman)
English (Bahasa Inggris)
Español - España (Bahasa Spanyol - Spanyol)
Español - Latinoamérica (Bahasa Spanyol - Amerika Latin)
Ελληνικά (Bahasa Yunani)
Français (Bahasa Prancis)
Italiano (Bahasa Italia)
Magyar (Bahasa Hungaria)
Nederlands (Bahasa Belanda)
Norsk (Bahasa Norwegia)
Polski (Bahasa Polandia)
Português (Portugis - Portugal)
Português-Brasil (Bahasa Portugis-Brasil)
Română (Bahasa Rumania)
Русский (Bahasa Rusia)
Suomi (Bahasa Finlandia)
Svenska (Bahasa Swedia)
Türkçe (Bahasa Turki)
Tiếng Việt (Bahasa Vietnam)
Українська (Bahasa Ukraina)
Laporkan kesalahan penerjemahan
Ask steam support, make ticket , because either security prevent make root folder, ( well known old rule with app dont should have access to ROOT folder.
But i had no issue make new folder at root, so maybe you have own NTFS issue with Folder user rights
Do note C-drev has more security sense its boot disk and OS for many ppl. ( even that matter and some folder even more. ( Document and Program files , hidden folder and so on, windows in itself so many NO NO's, or should said avoid them to reduce user mistakes. )
Other third part security app can raise security even further, try other location.
gl with it.
I mean steam backup and restore a game, is a simplified function, not even sure a user can make mistake here, this is why you should make ticket, it should just work with no issue at all.
And the more ticket they got about it, then they will test for such in the future, if they dont already do this.
ps.
Dont forget many of us dont even use that function, thats why make ticket is a nessary then you use that steam function.
The problem is the trailing period. The 'normal' Win32 file path handling APIs don't support certain characters in certain positions. But the actual NTFS filesystem has no problem with them. And if files or folders are created via other means than those old Win32 APIs, you can end up in a situation where files or folders exist in perfectly fine order in the file system but are inaccessible to many applications - including system applications such as Explorer, which still go through the old Win32 path handling.
The escape hatch is what OP already used:
Device paths that start with the leading \\? or \\.\ segment.
These work, because those paths are not sanitized, i.e. are not checked for 'illegal' characters, by the Win32 API before access.
Also seems to be missing stripe illegal characters in name then created, so many issue with this
It's just worse because you can't rename the backup folder manually anymore.