97.0.2 (32-bit) update ISSUES
I was working on my computer earlier today. Open FF and it asked to download an new update. I chose yes. A little later I closed out of FF and shortly after that got back into FF and the update installed. Now, windows for any application open and close slowly, almost like they are fading in when opening and fading out when closing.
Additionally, my taskbar, which is set to auto hide, very slowly un-hides and very slowly hides. All this was working fine before the install of FF 97.0.2 (32-bit) and became an issue immediately after the install (i.e., opening FF after downloading and closing FF).
Does anyone have any ideas on what the reason for this issue is? Did some setting get changed? Thanks.
ఎంపిక చేసిన పరిష్కారం
Please ignore my question regarding 97.0.2 (32-bit) update ISSUES. I tried to find a way to delete it since no one had responded yet but did not find a way to delete it.
After posting, I continue I research and try fixes (had tried a bunch of things before posting, including several reboots) and I finally found a NON-Mozilla answer to the problem.
The timing of my issue must have been completely coincidental to the installation of the FF 97.0.2 (32-bit) update.
I found a suggestion on the internet that it may be a graphics card problem. However, my drivers were up-to-date and tested fine.
The answer to my problem was resolved by looking at the Windows 10 Settings -> Windows Updates because I remembered that there are always optional updates and one group is optional Driver Updates. There were a bunch of driver updates that have been listed for a long item under Driver Updates but it is suggested to install them ONLY if needed: "If you have a specific problem, one of these drivers might help. Otherwise, automatic updates will keep your drivers up to date."
Since my 64-bit computer's graphic's card is PCI, I decided to try these three updates. At least one of the drivers, maybe all three together, fixed the problem after installation and reboot.
Intel - Other hardware - Intel(R) 8 Series/C220 Series PCI Express Root Port #3 - 8C14 Intel - Other hardware - Intel(R) 8 Series/C220 Series PCI Express Root Port #8 - 8C1E Intel - Other hardware - Intel(R) Xeon(R) processor E3 - 1200 v3/4th Gen Core processor PCI Express x16 Controller - 0C01
So, my problem is SOLVED and I do not think it was the FF Update that caused the problem.
ఈ సందర్భంలో ఈ సమాధానం చదవండి 👍 0ప్రత్యుత్తరాలన్నీ (1)
ఎంపిక చేసిన పరిష్కారం
Please ignore my question regarding 97.0.2 (32-bit) update ISSUES. I tried to find a way to delete it since no one had responded yet but did not find a way to delete it.
After posting, I continue I research and try fixes (had tried a bunch of things before posting, including several reboots) and I finally found a NON-Mozilla answer to the problem.
The timing of my issue must have been completely coincidental to the installation of the FF 97.0.2 (32-bit) update.
I found a suggestion on the internet that it may be a graphics card problem. However, my drivers were up-to-date and tested fine.
The answer to my problem was resolved by looking at the Windows 10 Settings -> Windows Updates because I remembered that there are always optional updates and one group is optional Driver Updates. There were a bunch of driver updates that have been listed for a long item under Driver Updates but it is suggested to install them ONLY if needed: "If you have a specific problem, one of these drivers might help. Otherwise, automatic updates will keep your drivers up to date."
Since my 64-bit computer's graphic's card is PCI, I decided to try these three updates. At least one of the drivers, maybe all three together, fixed the problem after installation and reboot.
Intel - Other hardware - Intel(R) 8 Series/C220 Series PCI Express Root Port #3 - 8C14 Intel - Other hardware - Intel(R) 8 Series/C220 Series PCI Express Root Port #8 - 8C1E Intel - Other hardware - Intel(R) Xeon(R) processor E3 - 1200 v3/4th Gen Core processor PCI Express x16 Controller - 0C01
So, my problem is SOLVED and I do not think it was the FF Update that caused the problem.