What purpose does the "BootTel.dat" file serve in MS WIN10 v.1709 protocols and/or processes? Just askin'. Any takers? According to some discussion boards, its not identifiable as any type of WIN10 1709 protocol or process norm. When properties is revealed, the ownership is "everyone" and some consider the file "suspect." As in spyware, malware, etc, or some component thereof. I'm okay with being disproven, but if I am right, show me the path to better security, please.
Got uBlock Origin and Ad Blocker Plus in effect in my browser and not using any other one right now, so creating a closed environment as control. Edge is our defense here. No crazy out of the box apps installed either that require legacy coding platforms, so bare bones MS only approved and deployed locally all around on my end, with only essential apps too. Gaming is gone. X-Box not necessary in my world.
IDEA: Removing dependencies to Internet Explorer (java=bad) in addition to WIN10 dependency on Win7(or any legacy C++ platform, for that matter),might be a good start, no? The more time on market, the more time trouble makers have to create the coding ugly to drop into my/our soup that enables command line coding to slip under the radar and execute commands that disable us from the protection we need on that train wreck we know as the internet. Most of the ugly seems to be in the win32 powershell world. payloads in .exe wrapper, so small files dropped in and slow decay of local endpoint defenses result.......hmmm......anyone else seeing that? Kinda obvious to me at this point, but I have been in that fight for awhile now.
Tried WIN 10S ("S" stand for sandbox?") awhile back, but not ready for primetime then. It was a bit too "S" on a few levels, from my experience, but definitely on the right track. It blocked even standard normal procedures, like, oh, Microsoft Store, for example. Identity mix-ups, locally. I just don't want to see things like the Chinese altering the Apple SDK / X-code Ghost nightmare I experienced 2 years ago, happen again. It made me an MS user after 15 years of Apple.
So let's keep up that good fight, guys and give me some insight on this if it is what I suspect it is. We have no other course of action, but to collectively defend our endpoints, daily. Every endpoint is a potential breach vector, whether we like it or not. So team time, if we want to survive this path we are currently on. Take a look at "Cybrary" - academic site. Its useful as well. If we are gonna lean on the machine, then know it and help keep it healthy.
Be well, be aware.