alabrand

I think the reason is because of a recent change in either Firefox or winapp2.ini. My guess is both. Perhaps it's due to the new cache location/system (dunno if it was cache or what it was, but something had changed which CCleaner had added in the recent version). Maybe it is , by fault, deleting an important file and Firefox can't repair it/re-create it? I dunno, I'm just rambling at this point. It's not like it'll affect me anymore since I'm staying away from winapp2.ini for now but I'd like to know what the cause of it all was.

I know my fair share of computers and such but when it comes to the majority of software and especially CCleaner and winapp2.ini, I'm pretty damn clueless as to what things do what. After having enabled pretty much everything in CCleaner for Firefox (excluding the corrupt sqlites, I believe) and run it a few times every now and then, my Firefox won't start properly (tried on two brand new Windows installations and two different Firefox versions, Aurora and Nightly, with the same CCleaner settings). When I click the firefox.exe it starts, but in the background and it stays there. I can't actually use it. I dunno which settings caused the error but I'm pretty damn sure it's something with winapp2.ini as this has never happened before. P.S. I'm on a brand new installation now running CCleaner without winapp2.ini and I have as of yet to encounter this problem.