New
#1
BootTel.dat
Curiosity has got the best of me! I have this file on my c drive and have no idea what it is. Cannot find any info on it?
Ron
BootTel.dat
-
-
New #2
A quick google search would suggest it may be malicious in some way. Best to run a malware scan and see what that says. dont run a quick scan tho, run a full scan.
-
New #3
I've been wondering about that BootTel.dat file myself. Neither Windows Defender or Malwarebytes complain about it and according to VirusTotal it's clean.
-
New #4
Likewise, nothing shows it to be dangerous but also nothing I can find shows what it is!
Ron
-
New #5
I'm not recommending this ...
Since I couldn't find any info on the BootTel.dat file, I decided to see if it's actually need for boot, etc. I renamed it BootTel.dat.bak and rebooted with no issues, then did a shut down and start up with no issues. Still no clue where it came from or what it is, but it didn't exist until 10/20/2017 according to it's file date.
-
New #6
My file date is 11/12/2017. OCD about explanations and there appears to be none for this file. Will delete it and go from there
Ron
-
New #7
Interesting. I can't find any scoop or usable info on this anywhere. Inspecting the file contents in Notepad++ doesn't shed any light, either. It's mostly made up of NUL characters with very little actual data, none of that amenable to "interpretation by inspection." But as a member of the "if it ain't broke, don't fix it" club I'll leave it be for now. Perhaps somebody else can come up with more info?
--Ed--
-
New #8
I wonder if that BootTel.dat has something to do with the 1709 manual update? IIRC, I waited a couple days to see if it would show up thru Windows Update and when it didn't, I manually updated both my systems using MCT / USB stick, around 10/20/2017.
-
-
New #9
Sorry for the necro, but for the search engine referals, I've found after running Puran Defrag on a non-bootable, storage HDD at boot time this file was created. Not sure if it was created by Puran itself, or just Windows as a result of an hour long chdsk/fix triggered by Puran.
-
New #10
Based on what you found, I would have to say that it was created by Windows as Puran Defrag was never ran on my machines however I was using Defraggler which very well could have caused Windows to set that file. Don't defrag anymore so I cannot try and recreate the issue.
Quote
