What are the amd64 files in Windows 7 x64?
Is it safe to delete "amd64" files from my Windows folder? My machine is a Dell using an Intel Processor, so why would I need AMD files?
If they are 'protected' how can I delete batches of them?
I am using Windows 7 x64 Ultimate
windows-7 64-bit
edited Sep 3 '11 at 23:59
Simon Sheehan
7,647124268
asked Sep 3 '11 at 23:52
NickNick
39112
add a comment |
Is it safe to delete "amd64" files from my Windows folder? My machine is a Dell using an Intel Processor, so why would I need AMD files?
If they are 'protected' how can I delete batches of them?
I am using Windows 7 x64 Ultimate
windows-7 64-bit
edited Sep 3 '11 at 23:59
Simon Sheehan
7,647124268
asked Sep 3 '11 at 23:52
NickNick
39112
2
Your OS is using your Intel processor in AMD64 mode. It might be an Intel CPU, but the current 64 bit extentions come from AMD, hence their name. (Intel had other 64 bit plans, look up Itanium if you are curious about those.)
– Hennes
Dec 7 '13 at 18:39
Zds is right, that they are Windows code, so don't remove them YOURSELF, but as Honest Guy Reno says, depending upon where they are... WELL... specifically, if they are in the WINSXS folder, microsoft is now giving you a utility to remove SOME of them: do an internet search on "desktop experience winsxs", or check out this link: blogs.technet.microsoft.com/askpfeplat/2014/05/13/…
– Doug_Ivison
Mar 2 '18 at 18:15
add a comment |
Is it safe to delete "amd64" files from my Windows folder? My machine is a Dell using an Intel Processor, so why would I need AMD files?
If they are 'protected' how can I delete batches of them?
I am using Windows 7 x64 Ultimate
windows-7 64-bit
edited Sep 3 '11 at 23:59
Simon Sheehan
7,647124268
asked Sep 3 '11 at 23:52
NickNick
39112
Is it safe to delete "amd64" files from my Windows folder? My machine is a Dell using an Intel Processor, so why would I need AMD files?
If they are 'protected' how can I delete batches of them?
I am using Windows 7 x64 Ultimate
windows-7 64-bit
windows-7 64-bit
edited Sep 3 '11 at 23:59
Simon Sheehan
7,647124268
asked Sep 3 '11 at 23:52
NickNick
39112
edited Sep 3 '11 at 23:59
Simon Sheehan
7,647124268
asked Sep 3 '11 at 23:52
NickNick
39112
edited Sep 3 '11 at 23:59
Simon Sheehan
7,647124268
edited Sep 3 '11 at 23:59
Simon Sheehan
7,647124268
edited Sep 3 '11 at 23:59
Simon Sheehan
7,647124268
7,647124268
asked Sep 3 '11 at 23:52
NickNick
39112
asked Sep 3 '11 at 23:52
NickNick
39112
asked Sep 3 '11 at 23:52
NickNick
39112
39112
2
Your OS is using your Intel processor in AMD64 mode. It might be an Intel CPU, but the current 64 bit extentions come from AMD, hence their name. (Intel had other 64 bit plans, look up Itanium if you are curious about those.)
– Hennes
Dec 7 '13 at 18:39
Zds is right, that they are Windows code, so don't remove them YOURSELF, but as Honest Guy Reno says, depending upon where they are... WELL... specifically, if they are in the WINSXS folder, microsoft is now giving you a utility to remove SOME of them: do an internet search on "desktop experience winsxs", or check out this link: blogs.technet.microsoft.com/askpfeplat/2014/05/13/…
– Doug_Ivison
Mar 2 '18 at 18:15
add a comment |
2
Your OS is using your Intel processor in AMD64 mode. It might be an Intel CPU, but the current 64 bit extentions come from AMD, hence their name. (Intel had other 64 bit plans, look up Itanium if you are curious about those.)
– Hennes
Dec 7 '13 at 18:39
Zds is right, that they are Windows code, so don't remove them YOURSELF, but as Honest Guy Reno says, depending upon where they are... WELL... specifically, if they are in the WINSXS folder, microsoft is now giving you a utility to remove SOME of them: do an internet search on "desktop experience winsxs", or check out this link: blogs.technet.microsoft.com/askpfeplat/2014/05/13/…
– Doug_Ivison
Mar 2 '18 at 18:15
2
2
Your OS is using your Intel processor in AMD64 mode. It might be an Intel CPU, but the current 64 bit extentions come from AMD, hence their name. (Intel had other 64 bit plans, look up Itanium if you are curious about those.)
– Hennes
Dec 7 '13 at 18:39
Your OS is using your Intel processor in AMD64 mode. It might be an Intel CPU, but the current 64 bit extentions come from AMD, hence their name. (Intel had other 64 bit plans, look up Itanium if you are curious about those.)
– Hennes
Dec 7 '13 at 18:39
Zds is right, that they are Windows code, so don't remove them YOURSELF, but as Honest Guy Reno says, depending upon where they are... WELL... specifically, if they are in the WINSXS folder, microsoft is now giving you a utility to remove SOME of them: do an internet search on "desktop experience winsxs", or check out this link: blogs.technet.microsoft.com/askpfeplat/2014/05/13/…
– Doug_Ivison
Mar 2 '18 at 18:15
Zds is right, that they are Windows code, so don't remove them YOURSELF, but as Honest Guy Reno says, depending upon where they are... WELL... specifically, if they are in the WINSXS folder, microsoft is now giving you a utility to remove SOME of them: do an internet search on "desktop experience winsxs", or check out this link: blogs.technet.microsoft.com/askpfeplat/2014/05/13/…
– Doug_Ivison
Mar 2 '18 at 18:15
add a comment |
3 Answers
3
active
oldest
votes
Do not. "AMD64" is the name for the 64-bit instruction set the x64 Windows runs on. It just happens to be AMD who invented the 64-bit x86 instruction set, which Intel copied later on.
answered Sep 3 '11 at 23:55
ZdsZds
2,1391115
(Similar to how Intel invented the 32-bit instruction set for x86, and AMD copied it later on.)
– grawity
Sep 4 '11 at 10:33
And amd64 is just "small extension" to "complete" x86 architecture developed (from scratch?) by Intel.
– Kamil
Nov 26 '14 at 15:42
add a comment |
Where the directory resides is important. You'll find files with these names in many locations. If they subtend a directory containing some string of fairly meaningless hexidecimal symbols, e.g., 12c8b0aaa7c55472e285280a, the subtending files and directories are probably garbage left over from an installation routine that was sloppily written.
First rename the aforementioned top level directory and run your computer for a couple days. If nothing seems amiss, then you're fairly safe deleting them. If they are locked, then you'll need to do some research on how to unlock them.
edited Dec 7 '13 at 17:21
Mokubai♦
57.1k16135154
answered Dec 7 '13 at 17:03
Honest Guy RenoHonest Guy Reno
111
add a comment |
Please DO NOT attempt to mess around with the system32 directory. There are two reasons:
This is ILLEGAL!
Messing around with system files is disgusting and messy! Most of these files are undocumented, but they usually waste space for no good reason.
Even though this is the case, messing around with these files CAN RENDER YOUR COMPUTER UNBOOTABLE!
P.S.: Please don't say I told you so!
answered Sep 10 '12 at 3:53
Jonathan RenoJonathan Reno
24729
7
-1 for the fearmongering and baseless "ILLEGAL" claim.
– ʇsәɹoɈ
Jul 5 '13 at 1:10
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f331656%2fwhat-are-the-amd64-files-in-windows-7-x64%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Do not. "AMD64" is the name for the 64-bit instruction set the x64 Windows runs on. It just happens to be AMD who invented the 64-bit x86 instruction set, which Intel copied later on.
answered Sep 3 '11 at 23:55
ZdsZds
2,1391115
(Similar to how Intel invented the 32-bit instruction set for x86, and AMD copied it later on.)
– grawity
Sep 4 '11 at 10:33
And amd64 is just "small extension" to "complete" x86 architecture developed (from scratch?) by Intel.
– Kamil
Nov 26 '14 at 15:42
add a comment |
Do not. "AMD64" is the name for the 64-bit instruction set the x64 Windows runs on. It just happens to be AMD who invented the 64-bit x86 instruction set, which Intel copied later on.
answered Sep 3 '11 at 23:55
ZdsZds
2,1391115
(Similar to how Intel invented the 32-bit instruction set for x86, and AMD copied it later on.)
– grawity
Sep 4 '11 at 10:33
And amd64 is just "small extension" to "complete" x86 architecture developed (from scratch?) by Intel.
– Kamil
Nov 26 '14 at 15:42
add a comment |
Do not. "AMD64" is the name for the 64-bit instruction set the x64 Windows runs on. It just happens to be AMD who invented the 64-bit x86 instruction set, which Intel copied later on.
answered Sep 3 '11 at 23:55
ZdsZds
2,1391115
Do not. "AMD64" is the name for the 64-bit instruction set the x64 Windows runs on. It just happens to be AMD who invented the 64-bit x86 instruction set, which Intel copied later on.
answered Sep 3 '11 at 23:55
ZdsZds
2,1391115
edited Dec 27 '18 at 4:33
answered Sep 3 '11 at 23:55
ZdsZds
2,1391115
answered Sep 3 '11 at 23:55
ZdsZds
2,1391115
answered Sep 3 '11 at 23:55
ZdsZds
2,1391115
2,1391115
(Similar to how Intel invented the 32-bit instruction set for x86, and AMD copied it later on.)
– grawity
Sep 4 '11 at 10:33
And amd64 is just "small extension" to "complete" x86 architecture developed (from scratch?) by Intel.
– Kamil
Nov 26 '14 at 15:42
add a comment |
(Similar to how Intel invented the 32-bit instruction set for x86, and AMD copied it later on.)
– grawity
Sep 4 '11 at 10:33
And amd64 is just "small extension" to "complete" x86 architecture developed (from scratch?) by Intel.
– Kamil
Nov 26 '14 at 15:42
(Similar to how Intel invented the 32-bit instruction set for x86, and AMD copied it later on.)
– grawity
Sep 4 '11 at 10:33
(Similar to how Intel invented the 32-bit instruction set for x86, and AMD copied it later on.)
– grawity
Sep 4 '11 at 10:33
And amd64 is just "small extension" to "complete" x86 architecture developed (from scratch?) by Intel.
– Kamil
Nov 26 '14 at 15:42
And amd64 is just "small extension" to "complete" x86 architecture developed (from scratch?) by Intel.
– Kamil
Nov 26 '14 at 15:42
add a comment |
Where the directory resides is important. You'll find files with these names in many locations. If they subtend a directory containing some string of fairly meaningless hexidecimal symbols, e.g., 12c8b0aaa7c55472e285280a, the subtending files and directories are probably garbage left over from an installation routine that was sloppily written.
First rename the aforementioned top level directory and run your computer for a couple days. If nothing seems amiss, then you're fairly safe deleting them. If they are locked, then you'll need to do some research on how to unlock them.
edited Dec 7 '13 at 17:21
Mokubai♦
57.1k16135154
answered Dec 7 '13 at 17:03
Honest Guy RenoHonest Guy Reno
111
add a comment |
Where the directory resides is important. You'll find files with these names in many locations. If they subtend a directory containing some string of fairly meaningless hexidecimal symbols, e.g., 12c8b0aaa7c55472e285280a, the subtending files and directories are probably garbage left over from an installation routine that was sloppily written.
First rename the aforementioned top level directory and run your computer for a couple days. If nothing seems amiss, then you're fairly safe deleting them. If they are locked, then you'll need to do some research on how to unlock them.
edited Dec 7 '13 at 17:21
Mokubai♦
57.1k16135154
answered Dec 7 '13 at 17:03
Honest Guy RenoHonest Guy Reno
111
add a comment |
Where the directory resides is important. You'll find files with these names in many locations. If they subtend a directory containing some string of fairly meaningless hexidecimal symbols, e.g., 12c8b0aaa7c55472e285280a, the subtending files and directories are probably garbage left over from an installation routine that was sloppily written.
First rename the aforementioned top level directory and run your computer for a couple days. If nothing seems amiss, then you're fairly safe deleting them. If they are locked, then you'll need to do some research on how to unlock them.
edited Dec 7 '13 at 17:21
Mokubai♦
57.1k16135154
answered Dec 7 '13 at 17:03
Honest Guy RenoHonest Guy Reno
111
Where the directory resides is important. You'll find files with these names in many locations. If they subtend a directory containing some string of fairly meaningless hexidecimal symbols, e.g., 12c8b0aaa7c55472e285280a, the subtending files and directories are probably garbage left over from an installation routine that was sloppily written.
First rename the aforementioned top level directory and run your computer for a couple days. If nothing seems amiss, then you're fairly safe deleting them. If they are locked, then you'll need to do some research on how to unlock them.
edited Dec 7 '13 at 17:21
Mokubai♦
57.1k16135154
answered Dec 7 '13 at 17:03
Honest Guy RenoHonest Guy Reno
111
edited Dec 7 '13 at 17:21
Mokubai♦
57.1k16135154
edited Dec 7 '13 at 17:21
Mokubai♦
57.1k16135154
edited Dec 7 '13 at 17:21
Mokubai♦
57.1k16135154
57.1k16135154
answered Dec 7 '13 at 17:03
Honest Guy RenoHonest Guy Reno
111
answered Dec 7 '13 at 17:03
Honest Guy RenoHonest Guy Reno
111
answered Dec 7 '13 at 17:03
Honest Guy RenoHonest Guy Reno
111
111
add a comment |
add a comment |
Please DO NOT attempt to mess around with the system32 directory. There are two reasons:
This is ILLEGAL!
Messing around with system files is disgusting and messy! Most of these files are undocumented, but they usually waste space for no good reason.
Even though this is the case, messing around with these files CAN RENDER YOUR COMPUTER UNBOOTABLE!
P.S.: Please don't say I told you so!
answered Sep 10 '12 at 3:53
Jonathan RenoJonathan Reno
24729
7
-1 for the fearmongering and baseless "ILLEGAL" claim.
– ʇsәɹoɈ
Jul 5 '13 at 1:10
add a comment |
Please DO NOT attempt to mess around with the system32 directory. There are two reasons:
This is ILLEGAL!
Messing around with system files is disgusting and messy! Most of these files are undocumented, but they usually waste space for no good reason.
Even though this is the case, messing around with these files CAN RENDER YOUR COMPUTER UNBOOTABLE!
P.S.: Please don't say I told you so!
answered Sep 10 '12 at 3:53
Jonathan RenoJonathan Reno
24729
7
-1 for the fearmongering and baseless "ILLEGAL" claim.
– ʇsәɹoɈ
Jul 5 '13 at 1:10
add a comment |
Please DO NOT attempt to mess around with the system32 directory. There are two reasons:
This is ILLEGAL!
Messing around with system files is disgusting and messy! Most of these files are undocumented, but they usually waste space for no good reason.
Even though this is the case, messing around with these files CAN RENDER YOUR COMPUTER UNBOOTABLE!
P.S.: Please don't say I told you so!
answered Sep 10 '12 at 3:53
Jonathan RenoJonathan Reno
24729
Please DO NOT attempt to mess around with the system32 directory. There are two reasons:
This is ILLEGAL!
Messing around with system files is disgusting and messy! Most of these files are undocumented, but they usually waste space for no good reason.
Even though this is the case, messing around with these files CAN RENDER YOUR COMPUTER UNBOOTABLE!
P.S.: Please don't say I told you so!
answered Sep 10 '12 at 3:53
Jonathan RenoJonathan Reno
24729
answered Sep 10 '12 at 3:53
Jonathan RenoJonathan Reno
24729
answered Sep 10 '12 at 3:53
Jonathan RenoJonathan Reno
24729
answered Sep 10 '12 at 3:53
Jonathan RenoJonathan Reno
24729
24729
7
-1 for the fearmongering and baseless "ILLEGAL" claim.
– ʇsәɹoɈ
Jul 5 '13 at 1:10
add a comment |
7
-1 for the fearmongering and baseless "ILLEGAL" claim.
– ʇsәɹoɈ
Jul 5 '13 at 1:10
7
7
-1 for the fearmongering and baseless "ILLEGAL" claim.
– ʇsәɹoɈ
Jul 5 '13 at 1:10
-1 for the fearmongering and baseless "ILLEGAL" claim.
– ʇsәɹoɈ
Jul 5 '13 at 1:10
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f331656%2fwhat-are-the-amd64-files-in-windows-7-x64%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
Your OS is using your Intel processor in AMD64 mode. It might be an Intel CPU, but the current 64 bit extentions come from AMD, hence their name. (Intel had other 64 bit plans, look up Itanium if you are curious about those.)
– Hennes
Dec 7 '13 at 18:39
Zds is right, that they are Windows code, so don't remove them YOURSELF, but as Honest Guy Reno says, depending upon where they are... WELL... specifically, if they are in the WINSXS folder, microsoft is now giving you a utility to remove SOME of them: do an internet search on "desktop experience winsxs", or check out this link: blogs.technet.microsoft.com/askpfeplat/2014/05/13/…
– Doug_Ivison
Mar 2 '18 at 18:15