UPDATE NOTICES ON CURRENT SIGNATURE

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Since we all seem to be in the same boat about updating, I think it would be
a help to ALL if someone (whoever knows these things!) would post EVERY day
what the current signautre is. Since mine SEEMS to be th current sig.
(1.14.1353.2) but Windows updates keep telling me I need to update and is
doing so automatically constantly, it would be great if we knew where we all
stand on this subject. I actually unchecked the auto update because iat is
totally unnecessary to keep having Windows update it, when it aopparently
doesn't need it. So there should be somewhere on this forum we can all go to
to see what is currently up to date. I can't understand why Microsoft can't
fix this problem. It is making me wish I hadn't uninsalled MSAV. It worked
great!!!
 
If you are getting repeated attempts to apply the same definition update,
then you are not up to date.

Applying the resolution steps in this article:
 
That no longer works for me. I get an error message and that is it! What is
the current signature? I posted the error message several days ago, but when
I turned off Spy Sweeper, it downloaded. Since then I haven't been "told" I
need an update.

WD tells me there is no update, but Windows Update has updated it many times
automatically.
To the 1.14.1353.2. Is that the latest signature?
 
Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1303.0
Signature Version: 1.14.1353.2
 
That number is the number of the current signatures, as Pat Willener has
shown.

However, the repeated offer of new signatures indicates a malfunction--for
whatever reason, the update mechanisms don't see that update as being in
place, and perhaps it is not.

Since the KB 915105 method has failed, the next thing I would try is the
Windows Installer Cleanup tool:

http://support.microsoft.com/?scid=kb;en-us;290301

However, this tool has a side effect which is significant--it appears to
prevent detection of missing Office patches at least until the next set of
definitions is in place. I don't have a workaround for this yet, so I'm not
sure I recommend this route.

If you do choose to use the installer cleanup, my recommendation is to
remove only "windows defender signatures" and not the program itself--which
is the next entry in the list.

Other than using the installer cleanup tool, you can try going to \program
files\windows defender, at a command prompt and typing:

msiexec /x as_sigs.msi

and hitting enter.
And, as a last ditch--some have reported success by uninstalling and
reinstalling the program.

I'm not real pleased with this set of steps--the problem with the cleanup
tools is a blow to my thinking here--that was effective, I'd found, and I
hadn't realized the side effect on Office updates.
 
Best way to know if you completely received the update is by looking at your
Event Viewer in Administrative tools if you don't receive any further
messages. Usually the problem was seen that the update icon in your toolbar
next to your clock would not go away. For a while dirctly after install, it
might, but then it would come back. Some people saw an error message, some
didn't. EVentually, the problem of the icon was fixed so that it would
disappear, but the installer would still not go through with the update. It
just appeared that it went through. That way, everyone would need to use the
msiexec /x string command to uninstall the previous update in order to
successfully install the new version. Finally, I can now say that by this
version, the updataes should be successful without any further manual changes.

Tip: The next time you go to update, no matter if you go through Windows
Update or Microsoft Upate or do it through the program "About" box, check
your version. As of now, you have the correct version. If your program can
confirm the exact same data, then it should be up to date. Here it is once
again:

Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1303.0
Signature Version: 1.14.1353.2

To check Administrative Tools->Event Viewer, a shortcut is to go to the
Start Menu and Select RUN-> Type "eventvwr" and press enter. Compare your
system and application logs and make sure that they don't say unsuccessful or
that they did not install. If you still should receive popups asking to
reinstall or you don't find the same signature version, then the update is
not complete. The usual command to install the previous update is to type the
following line on RUN, select Ok and Yes:

Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}

Once you type this into the RUN commandbox, press OK, and select Yes to
uninstall the current version update. This will allow the new one to be
installed. You can go to Windows Update or into the Help Messagebox to
install the new version. Check your places I mentioned above to make sure
there were no problems, but as I said earlier below in other messages, it
works. By now, those who install for the first time should not even have a
problem. Maybe even uninstalling completely then installing the most current
version, there should not be any trouble... Good Luck!
 
My version matches what you saym, but my Engine Version is 1.1.1186.0. So
apparently I am not up to date as WD tells me I am. Suggestions any different
than your instructions? Like I say when i go through about WD, it tells me I
am up to date, But if I go through Windows Update/Custom, it updates to the
same thing I have.


Jordon wrote

"Jindows Defender Version: 1.1.1051.0
 
What about the Signature version? The last update, on March 23rd, included
both Definition (Signatures) and an engine update.--so it appears you don't
have that one in place.

I'd go with Jordon's instructions starting at the "MSIEXEC" line.

--
 
The version Engine you have then is still the old version. It doesn't update
immediately like updates usually do. That update, if it is going to be for
the version I posted, it should have the new engine hopefully, so a one time
run of the msiexec uninstaller command will do the trick to complete the
install. What it does is remove the version you have currently so that the
new version can be installed. If the old version is not uninstalled, the new
one won't be able to take its place. Again, what to do is a simple 1 line
command and 2 button pushes. Here are the steps:

To UPDATE, first remove previous update by copying the following line, use
Start-> RUN and type or copy this line:

Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}

Then, go through Windows Defender Update Under the help menu box or through
Windows Updates, now called Microsoft Updates also... either place you go
should install everything completely. Restart may or may not be needed
depending if there are other installations available in Microsoft Update.
But, focus only on this install for now if you have the choice. Later, when
you go back to look at the box, you should have the most current version. The
version I have, so far all updates should be automatic now due to their new
engine. If you want to see detail of my step, just search "jmonkey" for other
posts answering basically the same problem or visit one example of the steps
I posted about 2 weeks ago at:
http://www.microsoft.com/athome/sec...f2d958-3085-4ffe-be7e-bc349efabf8e&sloc=en-US

Current Engine and Signature information is at least this value if not newer
Signature:
Windows Defender Version: 1.1.1051.0
Engine Version: 1.1.1303.0
Signature Version: 1.14.1353.2


Good luck!

-Jordan
 
Thank you so much. It worked. At first I didn't think so, but after a reboot
my Engione was the 1.1.1303.0....Will this update problem still continue or
is this a "permanent"
fix? I sure hope so as I spend half my computer time trying to "fix" WD.

Thanks again....
 
You're both very welcome!

Maybe the reboot was needed to lock in the update. When the computer
updates, it can have the data temporarily stored in memory, but if the
computer doesn't pass a verify command, the update won't stay. The harddrive
is a database of stored information or raw data made into user-friendly
environment. The information that was just changed was in registers. The
command you typed went into your registers and found the location of the
version you once had and removed the data to allow for updates. To ensure the
correct work was done, constraints are put on that string of data through
the windows environment to make sure no loss of the program. The old engine
somehow did not match the update, or whatever was passed into the engine did
not meet the condition to remove the old update successfully. Because the old
update did not remove, the new one could not be installed correctly.
Sometimes, you'd see a success, meaning the installation process was
successful, but when you look at the actual data, you found there were no
changes. If you have access to your Administrative tools, compare the last
time you installed and had problems. Short cut to that, use the Start->Run
command and type in (without quotes) "eventvwr" short for Event Viewer...
Click on Application and see what happened at that time, and click on System,
looking at about the same time, maybe a few seconds apart, you'll get a
success in the system, but the application will fail to install. I believe
that's the way it went.

Manually removing the old data with the command is what is usually put into
updates. Perhaps the engine contained the data, Engine referring to a
database that modifies the registry...contains the commands and strings of
code such as the one line I passed on to you... all of the information of the
storage of the program, Windows Defender. The new update contained the
correction necessary to allow installations to work. What you saw is usually
behind the scenes work. That box, when you copied that string "msiexec ..."
command is usually a silent command that automatically accepts yes to that
question.

Now, should you ever have a new update, there should not be a problem
(hopefully). I haven't seen one yet. This is a beta version. That's why there
tend to be the occasional bugs. So, this should be a permanent fix to the
problem, and I use the term lightly. New technology comes out all the time.
But it does look pretty good so far!

Enjoy the program!

Jordan
 
It's a "CRUD" relationship that I was talking about... CRUD stands for
Create, Read, Update, Delete; these are the 4 stages in updates. Should one
fail, the rest could not go on. It created the update, called instantiation,
your act of going to Microsoft Update... It read that you needed an update
and determined the proper version...it should also write, or update your
version with the new version, and then it deletes, finalizes, and stores
through a commit...part of the database. How it appears to succeed is on the
user side, but where it fails is on the computer side or server's side. It
could have been something small, but they fixed it. The new engine now
commits to the server's updates. That's the lesson of the day... class
dismissed!

Learn more about "CRUD" in msdn.microsoft.com..., research "engine". Ever
wish to know what a "search engine" really means... no it's not a mechanical
object. But it does have power! Explore for yourself! The power of knowledge
awaits at MSDN!

- Jmonkey
 
Sorry, I think you may be getting to deep into the "CRUD".... there are many
"views" on it's meaning. See website:
http://msdn.microsoft.com/library/default.asp?url=/archive/en-us/dnardevgen/html/desipat.asp

for more information on it if you'd like. . . do a 5 page paper for me, and
get back to me next week...

It was just a comparison using a funny word to play with on its uses with
database. Technically, the registers are a database for your Operating
system. I don't want to go off topic now, so if you're interested, database
is what's CRUD.

- Prof. Jmonkey
 
Hi

Well, my point was that this update process for a
lot of users is like "crud"/"junk", "software crud".

Waste from Redmond.......;)

And "perhaps" "maybe" MS could use kb:s/FAQs like a flowchart
and help users with problem. IMHO

They seems to have money to increase support quality....... ;)

regards
user plun
 
Hi Plun,

First of all, I'm not from MS. I'm a debugger like most who have answers
here along with other people who are from Microsoft. Some of us are just
trying to help those sort this problem out on the side of our own daily
tasks. Many people come with the same question and don't stop to look at
other logs posted with the correct answer. If you don't like the product, no
one says you need to keep using it, but it is a beta and it is free. A beta
program is still in test phase, the second step, the one that comes after the
Alpha phase. It is stable enough to be released, but occasionally, errors do
come up on different platforms as all beginning of software does. These are
not small programs. They use many other pieces of libraries and files that
may or may not be in your computer. Take a course in Object Oriented
Programming, you'll see how deep it can go.

The kb's are probably still in the development stage since this is a
pre-release "BETA" program. As they obtain the data through testing, changes
do go on thorugh updates, so making these flow charts, DFD's and such would
be too early. I haven't looked yet, but they could be out there somewhere.
Much chage goes on with design and implementation of programs all the time.
Just look at each operating system. Each operating system has similarities
and differences. From a broad perspective, sure, they look alike, but in
detail of how data flows, there is so much difference from one version to
another... part of optimization, part of keeping up with constant new
programs coming out and new versions, part of keeping up with new viruses
daily, partly new libraries of references to implement. The computer is
always changing although most users never see much other than updates being
downloaded and installed.

Now this program was released early for us, and it was for free! We will see
these changes occur over time. Some of us who installed the newest release of
the engine already see it. If you have trouble with the new updates, post
what's the problem and someone can post to help. Most of the time, the
problem is alredy solved several times on the list, so if you already see one
posted above, it will solve the problem. They've done a mighty fine job. CRUD
was a reference to an acronym for 4 stages in database update, no releation
to the crud in your eyes I assume due to not reading my last post. I
appologise if it confused you. Next time, I won't make such references.
Again, I do not work for Microsoft. I am here on occasion to help out those
who have had the same problem I had. This is just part of being a community
of testers of a new program who wish to help those in need. If you need
anything, create a new post, and someone will be there to help as soon as
they can.

Best wishes,
Jmonkey
 
Hello Jordan,

if you was back here a year ago like PLUN! You should be knowing better
to toke like this against PLUN, maybe there is now MVP behind the name
but in my ayes he is!! Search on PLUN on these newsgroups and read the
stuff he wrote and then maybe you start to understand PLUN ;)

Regards >*< TOM >*< (a other no MS debugger) ;)

Jordan Jmonkey H. schreef:
 
Hi

Well, I belieive that a giant as MS must fulfill some obligations
to a customer......

Nevertheless a Beta or not..... this is a "public beta" and
for sure it must be easy to make better FAQs and kb:s to help
users.

Or make simple "flowcharts" within blogs........

A lot of users which suffers with Spy/adware really needs
help.

We have a "subculture" now with cleaning forums instead of real and
better help from MS.

IMHO, just a proposal........ ;)

regards
plun
 
Back
Top