MSFN Forum: folder naturallanguage still exists - MSFN Forum

Jump to content



vLite Forum Rules

If you are having issues with Windows after removing components and have come to ask for help, please attach (not paste) your Last Session.ini file to your post to facilitate quicker assistance.
Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

folder naturallanguage still exists Rate Topic: -----

#1 User is offline   jaykay 

  • Newbie
  • Group: Members
  • Posts: 24
  • Joined: 28-June 08

Posted 18 October 2008 - 08:06 AM

hello,

5 minutes ago i saw that in c:\windows\winsxs are 4 folders wich have naturallanguage in their name.

x86_microsoft-windows-naturallanguage6_31bf3856ad364e35_6.0.6000.16710_none_9be9c78e2d9d5d54
x86_microsoft-windows-naturallanguage6_31bf3856ad364e35_6.0.6000.20867_none_9c4456c346dd3a34
x86_microsoft-windows-naturallanguage6_31bf3856ad364e35_6.0.6001.18098_none_9d81873e2afd9b5e
x86_microsoft-windows-naturallanguage6_31bf3856ad364e35_6.0.6001.22211_none_9e5aa34943e0a766

they are all 288mb big and contains 81 items.

are they belonging to the component natural language? im sure i removed this so im wondering....

and why are there two with 6000 in their names and two with 6001? do i need them, especially those with 6000?


jaykay

This post has been edited by jaykay: 18 October 2008 - 08:06 AM



#2 User is offline   MagicAndre1981 

  • after Windows 7 GA still Vista lover :)
  • Group: Patrons
  • Posts: 3,394
  • Joined: 28-August 05
  • OS:Vista Ultimate x86
  • Country: Country Flag

Posted 18 October 2008 - 12:56 PM

the 6000 are the RTM update files. They come from the update KB955020. I've left this update and blocked that update from WU

#3 User is offline   jaykay 

  • Newbie
  • Group: Members
  • Posts: 24
  • Joined: 28-June 08

Posted 19 October 2008 - 03:34 AM

i didnt understand a word, im sorry. and the kb is about the wrong spelling of five words, so why are the files so big? and can i delete them?

#4 User is offline   MagicAndre1981 

  • after Windows 7 GA still Vista lover :)
  • Group: Patrons
  • Posts: 3,394
  • Joined: 28-August 05
  • OS:Vista Ultimate x86
  • Country: Country Flag

Posted 19 October 2008 - 09:03 AM

6000 is the build number for Vista RTM, so all 6000.16xxx or 6000.20xxx files are updates for Vista RTM. The 6001.18xxx and 6001.22xxx files are the updates files for Vista Sp1.

To remove the files, uninstall the update KB955020 from Programs->Installed Updates and block it on WindowsUpdate (select hide this update)

#5 User is offline   fullfantom5 

  • Group: Members
  • Posts: 2
  • Joined: 06-May 08

Posted 21 October 2008 - 09:51 PM

Great tip.
I did recognize that this was occuping my winsxs folder more than 2G.
I couldn't remove the hot fix KB955020 but had to re-install my x64 vista.
This time I didn't install KB955020 and made sure it does have a whole difference. :thumbup

#6 User is offline   alvinkhorfire 

  • Member
  • PipPip
  • Group: Members
  • Posts: 103
  • Joined: 11-May 08

Posted 21 October 2008 - 11:59 PM

View PostMagicAndre1981, on Oct 19 2008, 11:03 PM, said:

6000 is the build number for Vista RTM, so all 6000.16xxx or 6000.20xxx files are updates for Vista RTM. The 6001.18xxx and 6001.22xxx files are the updates files for Vista Sp1.

To remove the files, uninstall the update KB955020 from Programs->Installed Updates and block it on WindowsUpdate (select hide this update)



Thanks, MagicAndre1981. Is there any unneccesary post-SP1 updates that will increase the file size although we have removed the component in vLite other than KB955020?

#7 User is offline   MagicAndre1981 

  • after Windows 7 GA still Vista lover :)
  • Group: Patrons
  • Posts: 3,394
  • Joined: 28-August 05
  • OS:Vista Ultimate x86
  • Country: Country Flag

Posted 22 October 2008 - 05:25 AM

Right now I don't know an update which will increase the WinSxS folder in such a way like the update KB955020 did.

#8 User is offline   jaykay 

  • Newbie
  • Group: Members
  • Posts: 24
  • Joined: 28-June 08

Posted 23 October 2008 - 02:33 AM

if i deinstall this update, the search-box in the start-menu doesnt work. same thing with the search-function in the explorer.

is that normal?^^

This post has been edited by jaykay: 23 October 2008 - 02:47 AM


#9 User is offline   MagicAndre1981 

  • after Windows 7 GA still Vista lover :)
  • Group: Patrons
  • Posts: 3,394
  • Joined: 28-August 05
  • OS:Vista Ultimate x86
  • Country: Country Flag

Posted 23 October 2008 - 03:01 PM

hmm, I've never uninstalled the fix. Try the same thing in a Virtual Machine: Install your Vista, install the updates and remove KB955020. Now check if your issue happens again.

#10 User is offline   fullfantom5 

  • Group: Members
  • Posts: 2
  • Joined: 06-May 08

Posted 23 October 2008 - 09:49 PM

Hey guys,

I did some comparison over vmware with vLited 64bit Home Premium SP1 without natural Language and amongst other stuff I've deleted.
From clean install, I only installed KB955020 to it and checked how much size it added to Winsxs folder.

---------------------------------
Before KB955020
2.74 GB size
2.80 GB size on disk

31,876 files 7,434 folders
---------------------------------
After KB955020
5.02 GB size
5.08 GB size on disk

32,540 files 7,442 folders
---------------------------------

As a result this patch definately spoils the whole vlite effort in terms of saving spaces.
I think this information is something to pass on to others who delete Natural Language but apply hotfixes automatically with windows update.

Jaykay>
Re-installing did kill the search engine like you've mention.
However on a non-vlited vista, uninstalling KB955020 won't kill the search engine but also doesn't fully uninstall, leaving winsxs contents as is.

Share this topic:


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy