• All Community
    • All Community
    • Forums
    • Ideas
    • Blogs
Advanced

Not what you are looking for? Ask the experts!

This forum thread needs a solution.
Kudos0

Leftover 16.1.0.33 files after upgrade to 16.2

I'm not sure why exactly, but in the C:\Program Files\Norton Internet Security directory there are 2 sub-directories: Branding and MUI.  Both of those contain a 16.1.0.33 directory, but no 16.2.0.7 directory.  The Engine directory contains a 16.2.0.7 and correctly removed the 16.1.0.33 directory.

I'm not sure why the Branding and MUI directories weren't update or even if they were supposed to be updated, but it seems strange that they still say 16.1.0.33.

Replies

Kudos0

Re: Leftover 16.1.0.33 files after upgrade to 16.2

I'm not sure why exactly, but in the C:\Program Files\Norton Internet Security directory there are 2 sub-directories: Branding and MUI.  Both of those contain a 16.1.0.33 directory, but no 16.2.0.7 directory.  The Engine directory contains a 16.2.0.7 and correctly removed the 16.1.0.33 directory.

I'm not sure why the Branding and MUI directories weren't update or even if they were supposed to be updated, but it seems strange that they still say 16.1.0.33.

Kudos0

Re: Leftover 16.1.0.33 files after upgrade to 16.2

Hi Morac,

Mine are the same - no problem.

Not all of the program files need to be modified for an updated version.

"Anyone who isn't confused really doesn't understand the situation."   Edward R. Murrow
Kudos0

Re: Leftover 16.1.0.33 files after upgrade to 16.2

Phil_D is correct.  :)

Not every LiveUpdate will update the Engine, MUI,or Branding patchs. folder.

bk

Kudos0

Re: Leftover 16.1.0.33 files after upgrade to 16.2

The 16.1.0.33 folder in Engine is not removed. Is there any problem?

Kudos0

Re: Leftover 16.1.0.33 files after upgrade to 16.2

Hi Whale,

Although I don't have the 16.1.0.33 engine folder this time, when the 16.1.0.33 version arrived in mid November I did have the previous engine folder left behind.

Sometimes portions of the previous versions are left behind for fallback reasons.

When did you receive the 16.2.0.7 update?

"Anyone who isn't confused really doesn't understand the situation."   Edward R. Murrow
Kudos0

Re: Leftover 16.1.0.33 files after upgrade to 16.2

Should be today... I am not sure... LiveUpdate did not ask me to restart computer this time...

Kudos0

Re: Leftover 16.1.0.33 files after upgrade to 16.2

Does "Help & Support" > "About" indicate that you have version 16.2.0.7?

See what happens after a restart.

"Anyone who isn't confused really doesn't understand the situation."   Edward R. Murrow
Kudos0

Re: Leftover 16.1.0.33 files after upgrade to 16.2

Yes, it is 16.2 already. I will try to restart later.

Kudos0

Re: Leftover 16.1.0.33 files after upgrade to 16.2

Let us know.
"Anyone who isn't confused really doesn't understand the situation."   Edward R. Murrow
Kudos0

Re: Leftover 16.1.0.33 files after upgrade to 16.2

Done! The 16.1.0.33 folder is disappeared. I believe that 2 reboots are necessary for "completing" the whole update. The first one is to activate the 16.2 engine and the second one is to delete the old 16.1 engine.

Kudos0

Re: Leftover 16.1.0.33 files after upgrade to 16.2

Thanks for the feedback.

Amazing what restarts can do!

"Anyone who isn't confused really doesn't understand the situation."   Edward R. Murrow

This thread is closed from further comment. Please visit the forum to start a new thread.