Your age, gender, height, weight, body temperature, heart rate, blood pressure, movement of belly as well as certain data about your daily activities, for example, your step taken, calories burned, sleep patterns and diary records when you use our healthcare products and services.They also collect your image, voice, location and unique identifiers that arguably constitute a digital fingerprint such as your MAC address.
I've faced this error once or twice before and I fixed it each time but alas I don't remember what the solution was. :(
Really feel stupid for not writing it down. *sigh*
Update: After conversing with Microsoft tech support for awhile I noticed that the computer was still resolving DNS addresses so at least something was connecting to the Internet somewhere (probably the DHCP client, right?). This helped me figure out that outgoing and incoming TCP and ICMP were both being blocked by the firewall. THAT was why Windows said I had no Internet. Microsoft had suggested the this possibility earler on but I dismissed it because I had uninstalled Eset's Internet Security and thought Windows would know better than to say I had no Internet merely becasue some protocols were blocked. Anyway I changed the firewall settings to allow ICMP packets, but the settings kept reverting to the previous rules. Then I figured out that this was actually a feature of Malwarebytes Windows Firewall Control, to protect your firewall settings from illicit alteration. I disabled that setting and this time the changes to the ICMP filtering took. I edited my firewall rules to allow outgoing TCP connections to port 80 and then my Internet started working again. Yay! I may have to enable some more rules to get other protocols working, but I'm happy so far with my progress.
Another Update: I've started getting the "No Internet, Secured" error again. :(
And this time IP addresses are NOT being resolved. It looks like the root cause of this error is different than last time. Will work on it some more later today, and come back here to post once I find a solution.
The "problem" turned out to be Malwarebytes Windows Firewall Control again- really not hard to find this time if you know where to look. Windows Firewall Control was set to "High filtering" mode which adds 2 firewall rules to the effect of turning off all Windows networking. It is controlled by a small little icon in the system tray, and all I had to do was right click and set it to the "Medium filtering" profile. Viola- Internet connectivity was restored.
I just took the Comptia Security+ certification exam via Pearson's onVUE online testing program. Now when I boot up I get the following error:
Pearson Vue, WHAT HAVE YOU DONE TO MY PC?
My installation of Eset's Nod32 anti-virus seemed to go off without a
hitch but when I attempt to run the program (either by clicking the
icon on the menu or executing it from the CLI) nothing happens. I
mean, the process executes and blocks input from the command line, and
it appears on a list of running processes, but there's no sign of it
DOING anything. No windows or error messages or dialog boxes or
I contacted Eset about this and it seems my distro, Gentoo, isn't
a supported platform (surprise!) so they're no help. I'm running a
recent version of KDE Plasma on Gentoo 64-bit, if it matters.
I had to execute the esets daemon manually before running the main program. The daemon is something like /opt/eset/esets/sbin/esets_daemon. That's off the top of my head, I forget the exect path. But once you run that (manually or in a rc file) the program just works as intended (I assume, I haven't done a scan with it yet).
Nearing the end of my malware recovery. Windows 10 is reinstalled, thoroughly hardened for security, and just about ready to go back online.
Yet there are a few significant problems I have yet to work out:
- Windows won't detect available wifi networks at login. I walk away and come back some hours later, yes, Windows will have found them but at log-in- NO.
- Once connected, half the Internet is nonfuctional. The WWW works and I can ping other computers on my network, but my antivirus won't update, I can't install disk imaging software I need to make a backup (the install program connects to the Internet to download its latest versions) and attempts to ping the outside world result in a sequence of "general failure"s. (That's with "ping /4". Attempts to ping with ICMPv6 don't even get past a DNS lookup.)
- Oh yeah and there's spotty Win10 behavior too which leads me to think my PC has surreptitiously been reinfected during my oh-so-brief excursions onto the 'net just trying to get the above to work. For awhile Windows' search fields weren't working and now the system's blocked up and refusing to let me run Windows Firewall.
Grrrrr. If the last part of those concerns ISN'T malware I'd hate to be the programmer responsible for letting the above bugs slip through his fingers- it's nearly indistinguishable.
I don't know; maybe I should system recover to a back up made just a couple days ago before I installed the newest Windows Update.
Eset Internet Security keeps reporting a "General compiler error" every time it tries to update. It started happening a few weeks ago and I ended up restoring my system from a backup, and I've spent the past couple weeks reinstalling my programs. Which seemed to solve the problem, but now I'm getting the compiler error again.
I obviously can't restore from a backup every two weeks. I googled for help and happened on a couple others reporting similar problems, but no fixes. Here's what I've tried so far:
Tried clearing the cache, didn't help.
Tried reinstalling Internet Security. It helped at first but the compiler error resurfaced some days later.
I think my PC is, despite my herculian precautions, infected with malware. So I tried using System Restore to restore to an earlier state, but it went bad what with the dots in the rollercoaster loop going around and around endlessly for over 24 hours. I eventually shut the thing off, and now can't even boot into Windows (attempting a normal boot just brings up a blank black screen, and attempting to boot into Recovery Mode results in a 0x0000001 error code with some complaint about Windows/System32/winload.exe):
Anyway off to the long overdue hardening of my Windows 10 computers.
Solution: It took me a day and a half to figure this out and I tried a bunch of things. First thing was to make sure "Remote Login" was checked under System Preferences > Sharing, and that it permitted all users to log in. After that I checked to make sure that my firewall wasn't blocking TCP on port 22. Finally I set up port forwarding on our router. Still didn't work.
After a LOT of googling, I tried checking the firewall again and discovered that I could login to the SSH server if I turned the firewall off. Ah-HA! I zeroed in on the firewall now and googled some, but all I found were false leads. Eventually I contacted customer support for Eset and they provided me with an explaination of how I can configure Eset to allow ssh connections to the ssh server.
Then I used it to install Emacs.
Before using Homebrew I had attempted to install Mitsuharu Yamamoto's Emacs distribution from source (Emacswiki really talked it up), but that didn't go so well as I quickly succumbed to dependency hell. First I needed to compile autoconf to generate the ./configure file I needed for the Emacs install- but that required that I download and compile makeinfo which required me to install Homebrew, then I needed to download and compile gnutls, which needed me to download and install nettle-2.5, but nettle-3.5 apparently wasn't good enough. Not wanting to downgrade to an earlier version of nettle I gave up on compiling it myself and installed the Homebrew precompiled binary version of Emacs with:
brew cask install emacs
That got me the vanilla official version from Emacs for macOSX. What I should have done was install the binary from the MacPorts package manager as that had Yamamoto's distro but I didn't see that option until I had already installed the official one. But it is installed and it works and it's going to be a lot better than editing text in nano (which is the only pre-installed text editor in macOS Catalina) or trying to use TextEdit (which twists your arm into writing richtext files or HTML instead of text files).