it was an ms tech, not me, who, after three hours on the phone and with
easy
assist, ran the sfc /scannow, and decided, without further probing,
that
the
source of the firewall problem lies in the unidentified corrupted, and
irreparable, files (*he* did not sfc /verifyonly - *i* did). he told me
that
i needed to reinstall vista from dvd - not something i look forward
to -
notwithstanding that i need the experience anyway. when i ran
/verifyonly,
and discovered that the only irreparably corrupted file was this "true
font"
.ttc, i was, as you can imagine, shocked!
when i installed onecare (4-5 weeks ago), windows firewall was
necessarily
rendered inoperative. 2 weeks later, i uninstalled onecare (i forget
the
details - either it was causing me trouble or it was not adequately
performing; in either case, i installed a 3rd party oa av, od av's, and
od
antispywares), and i have not been able to render windows firewall
operative.
another ms tech, 2 weeks ago, also had me on the phone for 3 hours;
after
reading a log (i forget which), he concluded that windows firewall *was
working* - even though it is reporting that it is not. nor is the
security
center. nor can i turn them on. i would certainly install a 3rd party
firewall, but i am worried about firewall conflict - remember, he said
that
windows firewall *is working*. so now i don't know - is windows
firewall
working or, as it's reporting itself, it is not? - it is possible that
i
have
not had a firewall for 3 weeks.
what symptoms manifest a firewall conflict (if i install the 3rd party
firewall, how will i know that i have a conflict?)
wrt the ie7 matter, that the second ms tech said must be premised on
the
(unidentified) corrupted files: it seems to have a problem with the
Ajax
technology, suchg as is found in gmail, and when i visit
www.techarp.com
(other sites continuously refresh so violently that the page never
loads)
.
:
I think you missed my point. System Restore is not a good way to
repair
corrupted files, if you don't know at what point the corrupted files
weren't
corrupt (using System Restore, you have to choose a date). SFC is
able
to
replace corrupted System files, but your issues may not be due to file
corruption. If SFC only found a font as problematic, then your
problems
most likely are caused by some other conflict, like the installation
of a
3rd party program. If you "cannot activate windows firewall, and
possibly
have other ie7 problems", and you tried SFC /scannow, then file
corruption
can be ruled out. You jumped to the wrong conclusion by equating
mingliu.ttc as the source of your issues. There's a wide gamut of
possibilities.
Now that we know that your Windows Firewall and IE7 files are
basically
intact and okay, specifically, what are the symptoms regarding Windows
Firewall? And your IE7 problems?
i question its value as a way to restore corrupted files
http://support.microsoft.com/default.aspx/kb/936212/en-us
this kb states:
"Using the System Restore tool may not necessarily help you
determine
the
issue. The System Restore tool uses restore points to return system
files
and
settings to an earlier point in time. You can use it to restore the
operating
system to a point in time in which you did not experience the issue.
When
you
use System Restore to restore the computer to a previous state, ***
programs
and updates that you installed are removed. ***"
as a newbie, this question may seem ridiculous because it is so
obvious:
why
would i want to remove all the antimalware that i carefully
configured?
all i
want to do is repair one or two corrupted files - not throw the baby
out
with
the bathwater.
as i just stated in another post, the sfc.exe /verifyonly >> cbs.txt
(all
35
MB of it!) produced the startling, psychedelic revelation that the
reason
that i cannot activate windows firewall, and possibly other ie7
problems,
is
due to a corruption of a file named mingliu.ttc - a windows "true
font"
file!! cbs.txt identifies this as *the only* sfc.exe /scannow
irrepartable
file!!
can this possibly be causing my windows firewall problem? and for
*this*,
i
am going to jeopardize my antimalware?
so, what can vista's restore feature be used for, with a net
benefit?
:
System Restore could be used to repair corrupted system files, but
you
would
have to choose a restore point with a date when the corrupted files
weren't
corrupted. Knowing when the files weren't corrupted may not be
easy
to
figure out.
why can't Vista's System Restore feature be used to repair
corrupted
files?
--
--Fool On The Hill
[32-bit Vista Home Premium]
It looks like you were able to sort out a few of your concerns.
Your
post
reminded me that I'd forgotten to tell you about making a
sfcdetails.txt
file, but it looks like you figured it out:
To create only SFC information gleaned from the cbs.log, and
find
the
sfcdetails.txt easily, open command prompt. By default, the
prompt
starts in
C:\Users\(Your Name). Type
cd desktop
Press Enter on your keyboard. Then type
findstr /c:"[SR]" %windir%\logs\cbs\cbs.log >sfcdetails.txt
Press Enter. Sfcdetails.txt should then appear on your Desktop.
I've run SFC with no problems found, or, as SFC puts it,
"Windows
Resource
Protection did not find any integrity violations". Here are my
locations
for
tcpmon.ini and settings.ini:
C:\Windows\System32\tcpmon.ini (Modified ‎September ‎19, ‎2006,
Created
November ‎02, ‎2006)
C:\Windows\winsxs\x86_microsoft-windows-p..rtmonitor-tcpmonini_31bf3856ad364e35_6.0.6000.16386_none_d04210aeaa5e863a\tcpmon.ini
(Modified ‎September ‎19, ‎2006, Created November ‎02, ‎2006)
C:\Program Files\Windows Sidebar\settings.ini (Modified and
Created
‎November ‎02, ‎2006)
C:\Windows\winsxs\x86_microsoft-windows-sidebar_31bf3856ad364e35_6.0.6000.16386_none_cca5e9c129bd0a02\settings.ini
(Modified and Created ‎November ‎02, ‎2006)
The C:\Windows\winsxs\ subfolders are where SFC crosschecks the
system
files
on your computer. For tcpmon.ini and settings.ini, under
C:\Windows\winsxs\, do you have the corresponding subfolders,
noted
above?
Like you, I don't see the two "irreparable" files as cause for
real
concern...
:
dean......... thanks for the reply. After reviewing your
answer
and
working
with Notepad and a KB article I found on the MS website, I
isolated
the
two
"irreparable" files as: tcpmon.ini and settings.ini. The
"tcpmon.ini"
works
with my new printer which works PERFECTLY with my Vista (though
much
of
the
time it's turned OFF) and the "settings.ini" fault has to do
with
the
Windows Sidebar, which I have disabled. No worries here, I
guess.
Whew!
Your reply gave me a good start into learning much about the
cbs.log
file
and how SFC works. Cheers.
EW
message
SFC appends its report to the cbs.log (i.e., it doesn't
create a
new
log
each time you run SFC). The latest info will be towards the
end
of
the
log
(it will be dated, under each POQ entry). The cbs.log file
is a
log
for
both SFC and the Windows Modules Installer service, which
installs
optional
features, updates, and service packs. Keep your eye on the
[SR]
tags,
in
the log, which are the System File Checker entries.
It's not possible to say whether or not you should be
concerned
about
your
irreparable files, without knowing what they are, and SFC's
reason
for
not
repairing them...
My new Vista system runs very fast and well. However, I ran
SFC
/verifyonly and got a 17MB file in the CBS.log folder. Lots
of
stuff
there that "looks" really scary, but what do I know!
Question: Later, I ran sfc /scannow and the result showed
that
some
system
files couldn't be repaired! I went to the cbs.log file and
saw
that
the
file was the one dated from the first sfc /verifyonly
process.
Isn't
there supposed to be a log from the ..../scannow process
also?
Finally, if my Vista runs flawlessly, should I be concerned
