About 7-8 times out of 10, starting Firefox in private mode (private browsing), the new "search field" or "search bar" (I don't know its proper name) located in the middle of the purple start page will not be clickable and will not work. Hovering the mouse cursor over that search field or bar will turn it from purple to white, clearly showing it as "blank" (no Google logo inside) and, as written above, the same search field cannot be used because "unclickable". My default search engine (just Google) will look like "not loaded" in that search field or bar (as written, no logo displayed in). Instead, if I write something (a keyword, a search term or an address) in the Firefox Address bar, even without closing, changing or refreshing that same firefox window, everything will be OK and Google will search it for me as usual: the problem is ONLY related to that search field (or "bar") placed in the middle of the purple start page of Firefox in "private browsing" mode. Please note: this problem NEVER occurs if ANY Firefox window in ANY mode (private or "regular") is ALREADY opened/started. I mean, if I start "private browsing" from the Firefox's jump list in the Windows task bar and there is NO instance of Firefox ALREADY running (I mean: no other Firefox window already opened), the problem occurs about 7-8 times out of 10, as written above. Otherwise, if Firefox is ALREADY running, I mean there is at least a Firefox window ALREADY opened, no matter in what mode (private mode or the "regular" one...), opening a new window in private mode will NEVER result in a "faulty" search bar/field in the middle of the usual "purple start page". It seems like the default search engine (for my Firefox: Google) has not enough time to be loaded, if I start a private window "from scratch". Instead, if there is any Firefox window already opened (i.e.: Firefos is already "started"), no problem will occur. By the way, I have tested my very same Firefox configuration duplicated on a virtual machine of mine and the problem NEVER occurs in ANY case because, I guess, that virtual machine runs veeery slowly and its virtualized Firefox takes A LOT to start and load (my host computer is too old and slow for virtualization). Below, some screenshots. Thanks.