How are you getting your new Firefox to recognize the old files? I have a thread on the "transplant" method here:

https://support.mozilla.org/en-US/questions/1322197#answer-1384732 -- of course your source folder will be on removable media or some other location

I'm short on time at the moment but I'll look it over and try later again. The issue is copying the profile over to the new computer (via USB drive) went just fine, but in about:profiles Firefox won't see that new profile folder is there. It's not listed on the Profiles list to select from but I can see it copied in full in File Explorer. I then created a new profile and then copied the contents of the other profile folder into that and while I can select that profile to use, it doesn't see any of the content still (cookies, logins, plugins, themes, etc). I had to set up everything manually best I could last night but I didn't focus too much more on it because I ran into Windows Update issues as well. I'm on metered bandwidth and that was too upsetting and I didn't go back to Firefox after. We now have less than half the bandwidth usage available because of MS and their stupid glitchy software and that has to carry me all the way through Oct 2nd and there are 2 other computers with updates coming up this next week to deal with still on top of it all :(

I'll double check your steps after dinner and reply back whichever way it goes. I appreciate the link for the possible solution.

Dropa, as I stated in my first message I've done it before, I know how to do it and something is wrong somewhere. I'm no beginner and have been using computers since the early 90s. I also want to point out the information you linked to does not show the proper links to the profile data. They are not located at the AppData level, they are located from there in both the Local & Roaming folders. That should be corrected by whomever wrote that article.

jscher2000, I've gone over your post and I did note you referenced the Roaming folder rather than Local. The last time I had to copy a profile to a new computer it was the Local folder which was one issue it seems. That did not resolve the issue on it's own as Firefox still would not auto detect the new copied profile on it's list. Creating a new profile and pointing it to the copied folder did work with that step. So, when exactly did it get changed so copying from the Local folder won't work, and any ideas why Firefox no longer auto detects the profiles added to the folders? There have been far too many updates on the browser since back in the day (I think I started using it at version 3 or something? Been a very long time now.) and not always for the good that's for sure. They pop updates out like out crazy every other week or so anymore and something always seems to get messed up or changed.

I appreciate the bits of help. It's been quite a few years since I had to copy a profile to a new computer and the experience is not what it used to be that's for sure. It was so much easier when Firefox auto detected the profile and you could just switch to that one from the profile preferences. Next up is Thunderbird and I'm assuming that has changed as well -_- Thanks again and here's hoping Thunderbird goes smoother. At least there's no add-ons to worry about setting up again there.

If you do not see a profile in the Profile Manager then it is likely that you didn't register this profile in profiles.ini as that file maps a profile to a location on the hard drive.

• https://support.mozilla.org/en-US/kb/how-run-firefox-when-profile-missing-inaccessible

cor-el, profiles.ini was copied over as well with the original renamed as a backup so that was not the issue. I had a printed paper from a page here in the past I originally used and that's the same steps I followed again for copying the profile to a new system and get it working. Firefox on the laptop still did not see the profile folder I had moved over so that was not the cause either. Sorry. Somewhere between that info in the past and trying to get it working now has clearly changed, likely from far too many updates pushed out constantly every other week for the browser. Something was changed somewhere.

The problem was already solved as I stated above.