Answered by:
windows\winsxs\amd* directory question

Question
-
I recently stumbled into the directory on the C: drive:
C:\windows\winsxs\amd*
...which contains many, many directories that start with amd. If I issue the command: dir g:\windows\winsxs\amd*/s in a Command.com box, I see 1/2 of a Gig of directories that start with amd.
Since my CPU is Intel, are these directories/files really necessary?
I'm not thinking that the files in winsxs are for 'hard links'. Well maybe they are, but do they apply to a PC that uses an Intel Processor? Also, there are similar forum posts done in the past, years back, about the WinSXS directory. I was wondering if anything has changed since then.
Example output follows below.
------------------------------------------------------------------------------------------------------------------------------------
02/10/2012 11:55 PM 5,426 amd64_wpf-windowsbase_31bf3856ad364e35_6.1.7601.21921_none_b60ee406778e10eb.manifest
07/13/2009 07:16 PM 2,199 amd64_wpf-windowsformsintegration_31bf3856ad364e35_6.1.7600.16385_none_5611010a95811832.manifest
07/13/2009 07:16 PM 1,799 amd64_wpf-winfxlist_31bf3856ad364e35_6.1.7600.16385_none_9cd1c50c09ba1b7a.manifest
07/13/2009 07:15 PM 2,035 amd64_wpf-winfxtargets_31bf3856ad364e35_6.1.7600.16385_none_252c8641bb943e1c.manifest
11/20/2010 08:18 PM 2,052 amd64_wpf-xamlviewer_31bf3856ad364e35_6.1.7601.17514_none_b43451f0938c6cd0.manifest
11/20/2010 08:13 PM 1,758 amd64_ws3cap.inf_31bf3856ad364e35_6.1.7601.17514_none_f4edf2835af3f471.manifest
04/12/2011 01:16 AM 1,934 amd64_wsdapi.resources_31bf3856ad364e35_6.1.7600.16385_en-us_772eb2557f1b8afb.manifest
11/20/2010 08:16 PM 6,539 amd64_wsdapi_31bf3856ad364e35_6.1.7601.17514_none_1cd9924263f62a5e.manifest
04/12/2011 01:16 AM 1,119 amd64_wsdprint.inf-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_8e3bb14c7b363416.manifest
04/12/2011 01:16 AM 1,786 amd64_wsdprint.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_8855223fb7fdd3ad.manifest
07/13/2009 10:28 PM 2,097 amd64_wsdprint.inf_31bf3856ad364e35_6.1.7600.16385_none_71442ff9caf7f629.manifest
04/12/2011 01:16 AM 1,119 amd64_wsdscdrv.inf-languagepack_31bf3856ad364e35_6.1.7600.16385_en-us_b5aa47205fce252f.manifest
04/12/2011 01:16 AM 2,620 amd64_wsdscdrv.inf.resources_31bf3856ad364e35_6.1.7600.16385_en-us_cbda9fbe5d91cc4e.manifest
07/13/2009 10:28 PM 2,097 amd64_wsdscdrv.inf_31bf3856ad364e35_6.1.7600.16385_none_2c33389ae33260ae.manifest
11/20/2010 08:13 PM 3,062 amd64_wstorflt.inf_31bf3856ad364e35_6.1.7601.17514_none_1eb9f40a2eecbab3.manifest
11/20/2010 08:13 PM 1,762 amd64_wstorvsc.inf_31bf3856ad364e35_6.1.7601.17514_none_856fd1bf7e8bad73.manifest
11/20/2010 08:13 PM 2,151 amd64_wudfusbcciddriver.inf_31bf3856ad364e35_6.1.7601.17514_none_c09fb51818544c63.manifest
11/20/2010 08:13 PM 4,349 amd64_wvmbus.inf_31bf3856ad364e35_6.1.7601.17514_none_97a6ab0ec0a6e89a.manifest
11/20/2010 08:13 PM 1.765 amd64_wvmbushid.inf_31bf3856ad364e35_6.1.7601.17514_none_4edc302bc3072c9f.manifest
11/20/2010 08:13 PM 2,419 amd64_wvmbusvideo.inf_31bf3856ad364e35_6.1.7601.17514_none_b15e703bf5d484e7.manifest
11/20/2010 08:13 PM 3,701 amd64_wvmic.inf_31bf3856ad364e35_6.1.7601.17514_none_6007c443630c03aa.manifest
04/27/2013 03:57 PM 880 amd64_wvpchbus.inf-languagepack_31bf3856ad364e35_7.1.7600.16393_ar-sa_66578a7c2e7053eb.manifest11106 File(s) 106,315,069 bytes
Total Files Listed:
13180 File(s) 547,377,325 bytes
used: Dos, MSDos, Win3, Win95, WinXP, Vista, Win7, and Win8 || AIX/Linux, etc: HP AIX, IBM AIX, Ubuntu, OpenSUSE, Puppy Linux, OS/2, VM/CMS, SAP
- Edited by DanMP Monday, May 20, 2013 5:08 AM typo
Monday, May 20, 2013 5:05 AM
Answers
-
AMD64 is the codename of the 64 Bit Windows. So yes, you need this files.
Microsoft Windows: x64 versions of Windows use the AMD64 moniker internally to designate various components which use or are compatible with this architecture. For example, the system directory on a Windows x64 Edition installation CD-ROM is named "AMD64", in contrast to "i386" in 32-bit versions.
http://en.wikipedia.org/wiki/X86-64#Industry_naming_conventions
"A programmer is just a tool which converts caffeine into code"
- Proposed as answer by Arthur Xie Tuesday, May 21, 2013 9:34 AM
- Marked as answer by Arthur Xie Wednesday, May 29, 2013 9:20 AM
Monday, May 20, 2013 6:14 AMAnswerer -
AMD developed this 64Bit architecture and named it this way. So it was ok to take this name.
"A programmer is just a tool which converts caffeine into code"
- Proposed as answer by Arthur Xie Tuesday, May 21, 2013 9:34 AM
- Marked as answer by Arthur Xie Wednesday, May 29, 2013 9:20 AM
Monday, May 20, 2013 7:29 PMAnswerer
All replies
-
AMD64 is the codename of the 64 Bit Windows. So yes, you need this files.
Microsoft Windows: x64 versions of Windows use the AMD64 moniker internally to designate various components which use or are compatible with this architecture. For example, the system directory on a Windows x64 Edition installation CD-ROM is named "AMD64", in contrast to "i386" in 32-bit versions.
http://en.wikipedia.org/wiki/X86-64#Industry_naming_conventions
"A programmer is just a tool which converts caffeine into code"
- Proposed as answer by Arthur Xie Tuesday, May 21, 2013 9:34 AM
- Marked as answer by Arthur Xie Wednesday, May 29, 2013 9:20 AM
Monday, May 20, 2013 6:14 AMAnswerer -
Well if MS was trying to be incognito by using 'AMD64' for a codename, they did a great job of it.
used: Dos, MSDos, Win3, Win95, WinXP, Vista, Win7, and Win8 || AIX/Linux, etc: HP AIX, IBM AIX, Ubuntu, OpenSUSE, Puppy Linux, OS/2, VM/CMS, SAP
Monday, May 20, 2013 11:31 AM -
AMD developed this 64Bit architecture and named it this way. So it was ok to take this name.
"A programmer is just a tool which converts caffeine into code"
- Proposed as answer by Arthur Xie Tuesday, May 21, 2013 9:34 AM
- Marked as answer by Arthur Xie Wednesday, May 29, 2013 9:20 AM
Monday, May 20, 2013 7:29 PMAnswerer