alchmo

sorry to burst the bubble, read the "Known Issues", it is said that it will stay that way, well if it stays that way, good luck with it the mentioning of Linux in that above statement is not true, Linux uses a complete different file and folder structure (access rights and all are handled different) comparing those is way of the course

it is, and for a number of reasons it leaves (either by intend or bug) the old folders still on the C: drive. it forces these folders with each profile creation on me again, so sorry that is not user friendly and the most important fact is, if any program forces me to adhere to its usage without giving me an option (and here im refering to the force install to C: of the program itself) it tries to patronize me, not help me. which is a no go for me if you are fine with this then all good for you, but i'm not (call me old but i will stay in control of my installations, and any program that does not work that way gets removed)

Sorry, yes i know you said you follow Microsoft recommendations to the letter, but force installing Vortex to C: is a no-go. there are a multitide of reason why this should not be done, if you wish to follow Microsoft guidelines then adhere to the "default Program installation place" that can be set in Windows 10. not force install to C: sorry to say it, i did wait for it, but the moment i saw this i only tested out abit and then removed it again, i won't be using it as long as it forces a install to C: on me default profile folders to be in the roaming profile, is a no go too, either let the user specify these folders during install/profile create, or dont create them with install/profile create until those settings have been set manually. dont create them and afterwards the user can change them, leaving him with those folders and files on C: as well as the new location it got moved too (and yes that is exactly what happened) program settings itself that are not connected to the profiles/etc. are fine in the roaming profile, but everything else not and the main reason for this is acknowledged by Microsoft as well, since todays system got a small SSD for C: and a normal HDD for data (usually D:) forcing anything on C: is a sure way to fill up that drive with unwanted data (slowing down the system as C: fills up, just take a look at the "default installation folders" settings in Windows 10, you can change it away from your C: drive, exactly for this reason!)

If you added OBSE later, i would advise to make a clean save and then use RoS anew. not sure if RoS does check for the presence of OBSE directly, or if OBSE is only needed for some functions. but using a clean save would be best if you think that the quest does not start. best make some backups of you current save. start Oblivion without the RoS esp active, load your save, save it in a different slot and exit Oblivion. activate RoS again and start Oblivion anew, load your prior saved game. This should reset everything from RoS to the start values from the mod