Tìm kiếm hỗ trợ

Tránh các lừa đảo về hỗ trợ. Chúng tôi sẽ không bao giờ yêu cầu bạn gọi hoặc nhắn tin đến số điện thoại hoặc chia sẻ thông tin cá nhân. Vui lòng báo cáo hoạt động đáng ngờ bằng cách sử dụng tùy chọn "Báo cáo lạm dụng".

Tìm hiểu thêm

Why is my home page set to https://www1.posnet.com.ar/webpos-frontend/context/start?

  • 6 trả lời
  • 3 gặp vấn đề này
  • 1 lượt xem
  • Trả lời mới nhất được viết bởi cardav

more options

I have set the home page to other URLs, but after restart, https://www1.posnet.com.ar/webpos-frontend/context/start is my home page. I have unistall and deleted all references to Mozilla manually.

I have set the home page to other URLs, but after restart, https://www1.posnet.com.ar/webpos-frontend/context/start is my home page. I have unistall and deleted all references to Mozilla manually.

Giải pháp được chọn

You can remove this local-settings.js file to disable using the mozilla.cfg file.
When this file is no longer present then you can remove the mozilla.cfg file as well.
If you would remove the mozilla.cfg file, but leave the local-settings.js then you wouldn't be able to start Firefox.
You can consider to leave the mozilla.cfg file, but set it to read-only.

Đọc câu trả lời này trong ngữ cảnh 👍 2

Tất cả các câu trả lời (6)

more options

If you do not keep changes after a restart or otherwise have problems with preferences, see:


Do a malware check with several malware scanning programs on the Windows computer.
Please scan with all programs because each program detects different malware.
All these programs have free versions.

Make sure that you update each program to get the latest version of their databases before doing a scan.

You can also do a check for a rootkit infection with TDSSKiller.

See also:

more options

I only ran Spybot, but earlier I had found the home page set in the mozilla.cfg file as follows:

pref("browser.startup.homepage","https://www1.posnet.com.ar/webpos-frontend/context/start");

I really don't know how it got there, but I commented it off, and now I am able to set the home page without any problems through the browser options.

Thank you for your prompt reply. I will continue to run the other malware programs.

more options

There shouldn't be a mozilla.fcg file present unless you've created it yourself to initialize some prefs.

This also involves the presence of a .js (JScript) file, probably in "defaults\pref" folder, that specifies to process this mozilla.cfg file.

If you have .js files apart from the channel-prefs.js file, that sets app.update.channel, in the defaults\pref folder then open this file in an editor like Notepad and please post its content.

If you have this mozilla.cfg file then best is to do a clean reinstall and delete the Firefox program folder before reinstalling a fresh copy of Firefox.

more options

Besides the \\program files (x86)\Mozilla Firefox\defaults\pref\channel-prefs.js file, there is one called local-settings.js, its contents are:

pref("general.config.obscure_value", 0); pref("general.config.filename", "mozilla.cfg");

If I uninstall/install again, this would be the 4th time. This is a brand new laptop and when I got it from our IT dept. it already had this problem. The second time I uninstall and reinstall. The third time I uninstall and then deleted the files in the \\Users\(user)\AppData directory. I have been downloading it from www.mozilla.org. I will download one more time and delete the mozilla directory from the programs folder.

more options

Giải pháp được chọn

You can remove this local-settings.js file to disable using the mozilla.cfg file.
When this file is no longer present then you can remove the mozilla.cfg file as well.
If you would remove the mozilla.cfg file, but leave the local-settings.js then you wouldn't be able to start Firefox.
You can consider to leave the mozilla.cfg file, but set it to read-only.

more options

I reinstalled one more time. The uninstall did not remove the local-settings.js, but did remove the mozilla.cfg file, so I removed the entire Mozzilla Firefox directory manually to get rid of the local-setting.js file, and now things are working normally. Thank you for your help.