Do more on the web, with a fast and secure browser!

Download Opera browser with:

  • built-in ad blocker
  • battery saver
  • free VPN
Download Opera

Problem signing in after moving roaming profile

  • I moved my roaming profile and opera refuses to sign me into my account.

    How can I fix it aside from reinstalling Opera?

  • @vince42 Please provide the necessary information as asked here

  • Your OS (Linux, Mac, Windows): Opera for Windows

    Your version of Opera: 50.0.2762.58 (PGO)

    If the problem is with a page, a link to it: not applicable

    A screen-shot of the problem if it's related to something not showing as should: not applicable

    A description of the problem, including as much as information as possible: I moved my roaming profile and opera refuses to sign me into my account.

    Steps to (try to) reproduce the issue: 1) move roaming profile, 2) start Opera, 3) try to enable synchronization

    Expected behavior and actual one: expected: sign in successful, actual: sign in not successful

    Looking forward for the solution.

  • @vince42

    Passwords will not work if you are using the profile on another Machine or with another User/Password.

    Is about this?

    If not,
    Clean cache and Cookies for Opera.com.


    Windows 10 (x64) | Anniversary Update
    Opera Stable 路 Beta 路 Developer

    Opera Test profile | Opera Reset / Back up LinuxMacWin

  • @vince42 said in Problem signing in after moving roaming profile:

    I moved my roaming profile and opera refuses to sign me into my account.

    Too vague. What exactly did you do and what is the error message?

  • @zalex108 said in Problem signing in after moving roaming profile:

    Passwords will not work if you are using the profile on another Machine or with another User/Password.

    Haven't tested this yet. What happens in this case? Does Opera act like there were never any passwords saved? Does saving new passwords work or do you have to delete the "Login Data" file first to get Opera to save passwords again (and perhaps do the export/ import thing)?

  • @vince42 said in Problem signing in after moving roaming profile:

    I moved my roaming profile and opera refuses to sign me into my account.

    How can I fix it aside from reinstalling Opera?

    what would happen if ya moved it back..

  • Thank you very much for the replies

    @zalex108 I am neither using the profile on another machine or with another user / password. I will try cleaning cache and cookies though.

    @leocg less vague: user profile - appdata - roaming - open properties - switch to location - press button Move - enter new location - press OK. Error message: "Snychronization - Something went wrong. An error occurred during the log-in process. Please try again."

    @nvmjustagirl Moving the roaming profile back would work, but is not a solution for my problem.

  • @vince42 Menu > About Opera shows the correct path to the profile directory?

  • @leocg Yes, the profile directory points to the correct location, while the cache path is still pointing to the old (no longer existing) folder.

  • @burnout426 said in Problem signing in after moving roaming profile:

    @zalex108 said in Problem signing in after moving roaming profile:

    Passwords will not work if you are using the profile on another Machine or with another User/Password.

    Haven't tested this yet. What happens in this case? Does Opera act like there were never any passwords saved? Does saving new passwords work or do you have to delete the "Login Data" file first to get Opera to save passwords again (and perhaps do the export/ import thing)?

    Right,
    It wipes the Login Data file, - no needs to be deleted -.

    So before, or Sync Passwords or Export/Import.

  • @vince42 said in Problem signing in after moving roaming profile:

    user profile - appdata - roaming - open properties - switch to location - press button Move - enter new location - press

    Ah, so you moved the whole Windows Roaming folder location. When you launch a command prompt, type set and hit enter, is the AppData variable's value set correctly to the new path? What about LocalAppData?

    Is the new location on another drive?

    while the cache path is still pointing to the old (no longer existing) folder.

    You moved the whole AppData/local folder too? Maybe Opera's not picking up the new location from that change and doesn't auto-create the missing cache folder if the whole local folder isn't where expected. Maybe syncing makes temp files in cache temporarily and that's failing.

    Try modifying Opera's shortcut to launcher.exe and add the "--disk-cache-dir=pathyouwant" switch to see if it makes any difference. If so, then you'll know what the issue is at least.

  • @burnout426 APPDATA is pointing to the new path, LOCALAPPDATA is correctly pointing to the old path.

    The new location of AppData\Roaming is on another drive.

    AppData\Local cannot be moved (although I wish it would be) and is still in the correct location.

    I really think that Roaming and Local AppDatas might be somehow out of sync - but Opera should recognize that and offer some kind of auto-repair like re-caching or whatever, as moving the roaming part of the profile is quite a regular scenario and works like charm with other applications.

    Testing the command line switch would not lead to new insights, as Opera already knows the correct location of AppData\Local (which is unchanged). I rather presume that something internal is confused.

    Maybe some directories should be deleted in AppData\Roaming or AppData\Local in order to force Opera to rebuild dependencies.

    I wish there were a tool, which would allow you to fix things internally.

  • Maybe you can try with a Symbolic Link.

  • @vince42 said in Problem signing in after moving roaming profile:

    AppData\Local cannot be moved (although I wish it would be) and is still in the correct location.

    Okay. Thought it could be as I have the option for it (Windows 10).

    @vince42 said in Problem signing in after moving roaming profile:

    Testing the command line switch would not lead to new insights, as Opera already knows the correct location of AppData\Local (which is unchanged).

    Okay. When you said the cache folder no longer exists, Opera isn't recreating it for you when it starts up or when you view web pages?

    @vince42 said in Problem signing in after moving roaming profile:

    I really think that Roaming and Local AppDatas might be somehow out of sync

    Might be. But, there's not much in Opera's local appdata folder, so it could be something in Opera's roaming folder. If Opera sync isn't working (allowing you to sign in), maybe you can find the sync files and clear them without having to start with a whole, new Opera profile. But, you'd want to make sure you find out how to do it in a way that doesn't blank out everything upstream. I wonder if it could be an issue with the Login Data file. Are all your password saved in Opera still and logging into everything else works fine?

  • @zalex108 Opera knows about the location of the AppData directories, as the about page states. Setting up symbolic links would rather create new confusion in the setup than solving things.

    I just would like to trace / log / check what Opera thinks it is doing and why it fails.

    Moving the roaming folder is a typical measure - and the expectation is that Opera would act as usually afterwards - but it does not. While all bookmarks etc are still there, the login into synchronization is broken and all user names and passwords for web sites seem to be gone.

    I just want to understand what happened, what the current problem is and how to fix it.

  • @burnout426 Yes, Windows gives you the option and fails to do so - thank you, Microsoft. 馃檪

    I misread the path of the cache folder the first time: the cache folder does exist and always existed and has not been rebuilt.

    Let's assume that the problem lies within the roaming folder. Can you tell me, which files are used for synchronization?

    All my user names and passwords are gone.

  • @vince42 said in Problem signing in after moving roaming profile:

    Can you tell me, which files are used for synchronization?

    Not sure, but when adding a bookmark or speeddial, I see SyncData.sqlite3 in the syncdata folder being modified with the new entry.

    If I was to try based on not knowing much, I'd close Opera, delete the syncdata folder, login data file (and journal file with it). Then, I'd start Opera and see if I could log in to sync again. If not, I'd close down Opera and look in the "Preferences" file for things I could delete related to sync. I'd back up the whole Opera roaming folder though first and restore the whole thing if none of that helped. Maybe someone else will know more details though.

  • @vince42 i think ya said you moved the whole Windows Roaming folder location.. The security attributes of the orginal has to be same as the new one.. Also if your using win 10.. sum of the files could have been locked.. not sure tho.. maybe ya could try in Safe Mode..

    i agree with zalex108 about Symbolic Link..

    mklink /j

    Do this once you're done moving the folder using the official way (Properties > Location).

    This command assumes you have moved the AppData\Roaming\ to D:\yourusernamehere\AppData\Roaming.

    mklink /j C:\Users\yourusernamehere\AppData\Roaming D:\yourusernamehere\AppData\Roaming

    Note this works best win 7 maybe with win 10 in safe mode

  • @burnout426 I will give that a try and yes, making a backup before executing such kind of operation is always a good idea. 馃槈 It's a shame that there is no good documentation for Opera, where we could read up all these questions. It would be very interesting to know which files are responsible for which features and are affected by which mechanisms.

    @nvmjustagirl Moving the roaming folder is a Windows feature, therefore all attributes are conserved. I had locked files during the move, but none of them was related to Opera. Making a symbolic link does not fix the problem at all as Opera does not have the problem that it cannot find the folder - it recognizes the folder locations. The suggested 'mklink /j' is considered to be deprecated, by the way.

Locked