Windows Explorer is taking 30 seconds to start. How can I find out why?
I have a new Core i3 notebook with Windows 7 Home Editon 64-bit. The PC ran fine for several months, but since a week, every time I try to open a folder on Explorer it takes almost 30 seconds to open.
So far, I've tried:
checking for virus or spyware with MS Essentials, MalwareBytes and DrWebCureIt (no virus or spyware)
restoring to a previous System Restore Point
chkdsk /f
(no errors)disabling Windows Search (no difference)
sfc /scannow
on a elevated command prompt. Stops with an error:
Windows Resource Protection could not perform the requested operation
disabling Active Destkop via registry (as explained in How to Disable or Enable Active Desktop in Windows 7)
disabling every non-Microsoft startup program via AutoRuns
disabling non-Microsoft shell extensions via ShellExView
removing USN JOURNAL with
fsutil usn deletejournal /D C:
because Sysinternals Process Monitor shows a delay of 5+ seconds on SFTLIST.EXE / FileSystemControl
The freeze is only in explorer.exe
, I can switch to another processes without any slowdown. There are no CPU spikes in Task Manager or Process Explorer.
I discard hardware errors because if I start in Safe Mode the PC ran fine.
I cannot do a repair install because Windows (Home Premium) is preinstalled in the notebook and I have no Windows CD.
What else can I try without having to reinstall Windows?
windows-7 windows freeze
add a comment |
I have a new Core i3 notebook with Windows 7 Home Editon 64-bit. The PC ran fine for several months, but since a week, every time I try to open a folder on Explorer it takes almost 30 seconds to open.
So far, I've tried:
checking for virus or spyware with MS Essentials, MalwareBytes and DrWebCureIt (no virus or spyware)
restoring to a previous System Restore Point
chkdsk /f
(no errors)disabling Windows Search (no difference)
sfc /scannow
on a elevated command prompt. Stops with an error:
Windows Resource Protection could not perform the requested operation
disabling Active Destkop via registry (as explained in How to Disable or Enable Active Desktop in Windows 7)
disabling every non-Microsoft startup program via AutoRuns
disabling non-Microsoft shell extensions via ShellExView
removing USN JOURNAL with
fsutil usn deletejournal /D C:
because Sysinternals Process Monitor shows a delay of 5+ seconds on SFTLIST.EXE / FileSystemControl
The freeze is only in explorer.exe
, I can switch to another processes without any slowdown. There are no CPU spikes in Task Manager or Process Explorer.
I discard hardware errors because if I start in Safe Mode the PC ran fine.
I cannot do a repair install because Windows (Home Premium) is preinstalled in the notebook and I have no Windows CD.
What else can I try without having to reinstall Windows?
windows-7 windows freeze
Is this happening with every folder, or only certain ones?
– Markus Orreilly
Aug 7 '12 at 22:29
@MarkusOrreilly: this is happening with every folder I try to open with Explorer. If I navigate the folders with Total Commander -for example- it works fine.
– PabloG
Aug 7 '12 at 23:12
add a comment |
I have a new Core i3 notebook with Windows 7 Home Editon 64-bit. The PC ran fine for several months, but since a week, every time I try to open a folder on Explorer it takes almost 30 seconds to open.
So far, I've tried:
checking for virus or spyware with MS Essentials, MalwareBytes and DrWebCureIt (no virus or spyware)
restoring to a previous System Restore Point
chkdsk /f
(no errors)disabling Windows Search (no difference)
sfc /scannow
on a elevated command prompt. Stops with an error:
Windows Resource Protection could not perform the requested operation
disabling Active Destkop via registry (as explained in How to Disable or Enable Active Desktop in Windows 7)
disabling every non-Microsoft startup program via AutoRuns
disabling non-Microsoft shell extensions via ShellExView
removing USN JOURNAL with
fsutil usn deletejournal /D C:
because Sysinternals Process Monitor shows a delay of 5+ seconds on SFTLIST.EXE / FileSystemControl
The freeze is only in explorer.exe
, I can switch to another processes without any slowdown. There are no CPU spikes in Task Manager or Process Explorer.
I discard hardware errors because if I start in Safe Mode the PC ran fine.
I cannot do a repair install because Windows (Home Premium) is preinstalled in the notebook and I have no Windows CD.
What else can I try without having to reinstall Windows?
windows-7 windows freeze
I have a new Core i3 notebook with Windows 7 Home Editon 64-bit. The PC ran fine for several months, but since a week, every time I try to open a folder on Explorer it takes almost 30 seconds to open.
So far, I've tried:
checking for virus or spyware with MS Essentials, MalwareBytes and DrWebCureIt (no virus or spyware)
restoring to a previous System Restore Point
chkdsk /f
(no errors)disabling Windows Search (no difference)
sfc /scannow
on a elevated command prompt. Stops with an error:
Windows Resource Protection could not perform the requested operation
disabling Active Destkop via registry (as explained in How to Disable or Enable Active Desktop in Windows 7)
disabling every non-Microsoft startup program via AutoRuns
disabling non-Microsoft shell extensions via ShellExView
removing USN JOURNAL with
fsutil usn deletejournal /D C:
because Sysinternals Process Monitor shows a delay of 5+ seconds on SFTLIST.EXE / FileSystemControl
The freeze is only in explorer.exe
, I can switch to another processes without any slowdown. There are no CPU spikes in Task Manager or Process Explorer.
I discard hardware errors because if I start in Safe Mode the PC ran fine.
I cannot do a repair install because Windows (Home Premium) is preinstalled in the notebook and I have no Windows CD.
What else can I try without having to reinstall Windows?
windows-7 windows freeze
windows-7 windows freeze
edited Aug 7 '12 at 22:57
Der Hochstapler
68k50230286
68k50230286
asked Aug 7 '12 at 22:09
PabloGPabloG
52441021
52441021
Is this happening with every folder, or only certain ones?
– Markus Orreilly
Aug 7 '12 at 22:29
@MarkusOrreilly: this is happening with every folder I try to open with Explorer. If I navigate the folders with Total Commander -for example- it works fine.
– PabloG
Aug 7 '12 at 23:12
add a comment |
Is this happening with every folder, or only certain ones?
– Markus Orreilly
Aug 7 '12 at 22:29
@MarkusOrreilly: this is happening with every folder I try to open with Explorer. If I navigate the folders with Total Commander -for example- it works fine.
– PabloG
Aug 7 '12 at 23:12
Is this happening with every folder, or only certain ones?
– Markus Orreilly
Aug 7 '12 at 22:29
Is this happening with every folder, or only certain ones?
– Markus Orreilly
Aug 7 '12 at 22:29
@MarkusOrreilly: this is happening with every folder I try to open with Explorer. If I navigate the folders with Total Commander -for example- it works fine.
– PabloG
Aug 7 '12 at 23:12
@MarkusOrreilly: this is happening with every folder I try to open with Explorer. If I navigate the folders with Total Commander -for example- it works fine.
– PabloG
Aug 7 '12 at 23:12
add a comment |
4 Answers
4
active
oldest
votes
Run Process Monitor.
Enable Duration column.
Start Explorer.
Wait for the delay to pass.
Stop recording events in Process Monitor (Ctrl+E).
Open the Filters (Ctrl+L).
Add a new filter that includes all items with a Duration of 1 or more.
You will now see only those events, that took longer than 1 second to complete. This may be able to give you an indication about what is delaying the start of Explorer.
If there are still too many events listed, you can increase the duration in the filter.
You can also try to read through the log and see what explorer.exe
is doing when it starts.
that's exactly the way I found the processes that takes 5 seconds (only that I filtered with 0.5 sec). The process/operation listed -as posted- is SFTLIST.EXE / FileSystemControl with 5 or more seconds
– PabloG
Aug 7 '12 at 23:08
@PabloG: Does it show only 1 entry in the filtered results? Or are there multiple operations performed bysftlist.exe
that each took 5 seconds? And most importantly, what operations were those?
– Der Hochstapler
Aug 7 '12 at 23:10
there are four 5 sec+ operations for each Explorer click on a folder: the process is SFTLIST.EXE, the operation is FileSystemControl. Before I disabled the USN Journal, the operation was USN_JOURNAL_UPDATE or something like that (didn't saved the log)
– PabloG
Aug 7 '12 at 23:54
@PabloG: What does it say in the Details column for thosesftlist.exe
processes?
– Der Hochstapler
Aug 7 '12 at 23:59
@PabloG: The process seems to be the Application Virtualization client service. From what I've been reading about it, I don't think I've ever used it. I'm not finding any similar issues online right now. Could you check the event log regarding this service?
– Der Hochstapler
Aug 8 '12 at 0:05
|
show 2 more comments
Wow, that's quite the list of things you've tried. One other thing I would try as more of a diagnostic step would be to force-kill explorer.exe and then start it again. If it behaves differently, it might give you some additional info to go off of.
Force kill explorer.exe:
taskkill /f /im explorer.exe
Then start explorer.exe just by running it:
explorer.exe
If I think of anymore things to try I'll put them in here as well.
yeah, I did it, no luck
– PabloG
Aug 7 '12 at 23:05
Doesn't help me
– B T
Jan 14 '16 at 21:54
add a comment |
If sfc
is returning
Windows Resource Protection could not perform the requested operation
I assume you didn't do a full sfc scan? Why don't you try the suggestions here to get sfc /scannow to work again.
If that doesn't help, uploading a full Process Monitor log of what happens when you start up Explorer could help diagnose the problem.
add a comment |
I have come here because I had the same problem. Windows File Explorer taking about 20 seconds to start up as well as some other processes with the same delay. The answers didn't help me much, but I found a network drive to not be responding properly. I managed to restore it to operations and voilà everything worked fine again. It turned out, that my %TEMP% was mapped to the non-functioning network drive. That might have played a major role in the startup delay.
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%2f458861%2fwindows-explorer-is-taking-30-seconds-to-start-how-can-i-find-out-why%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Run Process Monitor.
Enable Duration column.
Start Explorer.
Wait for the delay to pass.
Stop recording events in Process Monitor (Ctrl+E).
Open the Filters (Ctrl+L).
Add a new filter that includes all items with a Duration of 1 or more.
You will now see only those events, that took longer than 1 second to complete. This may be able to give you an indication about what is delaying the start of Explorer.
If there are still too many events listed, you can increase the duration in the filter.
You can also try to read through the log and see what explorer.exe
is doing when it starts.
that's exactly the way I found the processes that takes 5 seconds (only that I filtered with 0.5 sec). The process/operation listed -as posted- is SFTLIST.EXE / FileSystemControl with 5 or more seconds
– PabloG
Aug 7 '12 at 23:08
@PabloG: Does it show only 1 entry in the filtered results? Or are there multiple operations performed bysftlist.exe
that each took 5 seconds? And most importantly, what operations were those?
– Der Hochstapler
Aug 7 '12 at 23:10
there are four 5 sec+ operations for each Explorer click on a folder: the process is SFTLIST.EXE, the operation is FileSystemControl. Before I disabled the USN Journal, the operation was USN_JOURNAL_UPDATE or something like that (didn't saved the log)
– PabloG
Aug 7 '12 at 23:54
@PabloG: What does it say in the Details column for thosesftlist.exe
processes?
– Der Hochstapler
Aug 7 '12 at 23:59
@PabloG: The process seems to be the Application Virtualization client service. From what I've been reading about it, I don't think I've ever used it. I'm not finding any similar issues online right now. Could you check the event log regarding this service?
– Der Hochstapler
Aug 8 '12 at 0:05
|
show 2 more comments
Run Process Monitor.
Enable Duration column.
Start Explorer.
Wait for the delay to pass.
Stop recording events in Process Monitor (Ctrl+E).
Open the Filters (Ctrl+L).
Add a new filter that includes all items with a Duration of 1 or more.
You will now see only those events, that took longer than 1 second to complete. This may be able to give you an indication about what is delaying the start of Explorer.
If there are still too many events listed, you can increase the duration in the filter.
You can also try to read through the log and see what explorer.exe
is doing when it starts.
that's exactly the way I found the processes that takes 5 seconds (only that I filtered with 0.5 sec). The process/operation listed -as posted- is SFTLIST.EXE / FileSystemControl with 5 or more seconds
– PabloG
Aug 7 '12 at 23:08
@PabloG: Does it show only 1 entry in the filtered results? Or are there multiple operations performed bysftlist.exe
that each took 5 seconds? And most importantly, what operations were those?
– Der Hochstapler
Aug 7 '12 at 23:10
there are four 5 sec+ operations for each Explorer click on a folder: the process is SFTLIST.EXE, the operation is FileSystemControl. Before I disabled the USN Journal, the operation was USN_JOURNAL_UPDATE or something like that (didn't saved the log)
– PabloG
Aug 7 '12 at 23:54
@PabloG: What does it say in the Details column for thosesftlist.exe
processes?
– Der Hochstapler
Aug 7 '12 at 23:59
@PabloG: The process seems to be the Application Virtualization client service. From what I've been reading about it, I don't think I've ever used it. I'm not finding any similar issues online right now. Could you check the event log regarding this service?
– Der Hochstapler
Aug 8 '12 at 0:05
|
show 2 more comments
Run Process Monitor.
Enable Duration column.
Start Explorer.
Wait for the delay to pass.
Stop recording events in Process Monitor (Ctrl+E).
Open the Filters (Ctrl+L).
Add a new filter that includes all items with a Duration of 1 or more.
You will now see only those events, that took longer than 1 second to complete. This may be able to give you an indication about what is delaying the start of Explorer.
If there are still too many events listed, you can increase the duration in the filter.
You can also try to read through the log and see what explorer.exe
is doing when it starts.
Run Process Monitor.
Enable Duration column.
Start Explorer.
Wait for the delay to pass.
Stop recording events in Process Monitor (Ctrl+E).
Open the Filters (Ctrl+L).
Add a new filter that includes all items with a Duration of 1 or more.
You will now see only those events, that took longer than 1 second to complete. This may be able to give you an indication about what is delaying the start of Explorer.
If there are still too many events listed, you can increase the duration in the filter.
You can also try to read through the log and see what explorer.exe
is doing when it starts.
answered Aug 7 '12 at 22:53
Der HochstaplerDer Hochstapler
68k50230286
68k50230286
that's exactly the way I found the processes that takes 5 seconds (only that I filtered with 0.5 sec). The process/operation listed -as posted- is SFTLIST.EXE / FileSystemControl with 5 or more seconds
– PabloG
Aug 7 '12 at 23:08
@PabloG: Does it show only 1 entry in the filtered results? Or are there multiple operations performed bysftlist.exe
that each took 5 seconds? And most importantly, what operations were those?
– Der Hochstapler
Aug 7 '12 at 23:10
there are four 5 sec+ operations for each Explorer click on a folder: the process is SFTLIST.EXE, the operation is FileSystemControl. Before I disabled the USN Journal, the operation was USN_JOURNAL_UPDATE or something like that (didn't saved the log)
– PabloG
Aug 7 '12 at 23:54
@PabloG: What does it say in the Details column for thosesftlist.exe
processes?
– Der Hochstapler
Aug 7 '12 at 23:59
@PabloG: The process seems to be the Application Virtualization client service. From what I've been reading about it, I don't think I've ever used it. I'm not finding any similar issues online right now. Could you check the event log regarding this service?
– Der Hochstapler
Aug 8 '12 at 0:05
|
show 2 more comments
that's exactly the way I found the processes that takes 5 seconds (only that I filtered with 0.5 sec). The process/operation listed -as posted- is SFTLIST.EXE / FileSystemControl with 5 or more seconds
– PabloG
Aug 7 '12 at 23:08
@PabloG: Does it show only 1 entry in the filtered results? Or are there multiple operations performed bysftlist.exe
that each took 5 seconds? And most importantly, what operations were those?
– Der Hochstapler
Aug 7 '12 at 23:10
there are four 5 sec+ operations for each Explorer click on a folder: the process is SFTLIST.EXE, the operation is FileSystemControl. Before I disabled the USN Journal, the operation was USN_JOURNAL_UPDATE or something like that (didn't saved the log)
– PabloG
Aug 7 '12 at 23:54
@PabloG: What does it say in the Details column for thosesftlist.exe
processes?
– Der Hochstapler
Aug 7 '12 at 23:59
@PabloG: The process seems to be the Application Virtualization client service. From what I've been reading about it, I don't think I've ever used it. I'm not finding any similar issues online right now. Could you check the event log regarding this service?
– Der Hochstapler
Aug 8 '12 at 0:05
that's exactly the way I found the processes that takes 5 seconds (only that I filtered with 0.5 sec). The process/operation listed -as posted- is SFTLIST.EXE / FileSystemControl with 5 or more seconds
– PabloG
Aug 7 '12 at 23:08
that's exactly the way I found the processes that takes 5 seconds (only that I filtered with 0.5 sec). The process/operation listed -as posted- is SFTLIST.EXE / FileSystemControl with 5 or more seconds
– PabloG
Aug 7 '12 at 23:08
@PabloG: Does it show only 1 entry in the filtered results? Or are there multiple operations performed by
sftlist.exe
that each took 5 seconds? And most importantly, what operations were those?– Der Hochstapler
Aug 7 '12 at 23:10
@PabloG: Does it show only 1 entry in the filtered results? Or are there multiple operations performed by
sftlist.exe
that each took 5 seconds? And most importantly, what operations were those?– Der Hochstapler
Aug 7 '12 at 23:10
there are four 5 sec+ operations for each Explorer click on a folder: the process is SFTLIST.EXE, the operation is FileSystemControl. Before I disabled the USN Journal, the operation was USN_JOURNAL_UPDATE or something like that (didn't saved the log)
– PabloG
Aug 7 '12 at 23:54
there are four 5 sec+ operations for each Explorer click on a folder: the process is SFTLIST.EXE, the operation is FileSystemControl. Before I disabled the USN Journal, the operation was USN_JOURNAL_UPDATE or something like that (didn't saved the log)
– PabloG
Aug 7 '12 at 23:54
@PabloG: What does it say in the Details column for those
sftlist.exe
processes?– Der Hochstapler
Aug 7 '12 at 23:59
@PabloG: What does it say in the Details column for those
sftlist.exe
processes?– Der Hochstapler
Aug 7 '12 at 23:59
@PabloG: The process seems to be the Application Virtualization client service. From what I've been reading about it, I don't think I've ever used it. I'm not finding any similar issues online right now. Could you check the event log regarding this service?
– Der Hochstapler
Aug 8 '12 at 0:05
@PabloG: The process seems to be the Application Virtualization client service. From what I've been reading about it, I don't think I've ever used it. I'm not finding any similar issues online right now. Could you check the event log regarding this service?
– Der Hochstapler
Aug 8 '12 at 0:05
|
show 2 more comments
Wow, that's quite the list of things you've tried. One other thing I would try as more of a diagnostic step would be to force-kill explorer.exe and then start it again. If it behaves differently, it might give you some additional info to go off of.
Force kill explorer.exe:
taskkill /f /im explorer.exe
Then start explorer.exe just by running it:
explorer.exe
If I think of anymore things to try I'll put them in here as well.
yeah, I did it, no luck
– PabloG
Aug 7 '12 at 23:05
Doesn't help me
– B T
Jan 14 '16 at 21:54
add a comment |
Wow, that's quite the list of things you've tried. One other thing I would try as more of a diagnostic step would be to force-kill explorer.exe and then start it again. If it behaves differently, it might give you some additional info to go off of.
Force kill explorer.exe:
taskkill /f /im explorer.exe
Then start explorer.exe just by running it:
explorer.exe
If I think of anymore things to try I'll put them in here as well.
yeah, I did it, no luck
– PabloG
Aug 7 '12 at 23:05
Doesn't help me
– B T
Jan 14 '16 at 21:54
add a comment |
Wow, that's quite the list of things you've tried. One other thing I would try as more of a diagnostic step would be to force-kill explorer.exe and then start it again. If it behaves differently, it might give you some additional info to go off of.
Force kill explorer.exe:
taskkill /f /im explorer.exe
Then start explorer.exe just by running it:
explorer.exe
If I think of anymore things to try I'll put them in here as well.
Wow, that's quite the list of things you've tried. One other thing I would try as more of a diagnostic step would be to force-kill explorer.exe and then start it again. If it behaves differently, it might give you some additional info to go off of.
Force kill explorer.exe:
taskkill /f /im explorer.exe
Then start explorer.exe just by running it:
explorer.exe
If I think of anymore things to try I'll put them in here as well.
answered Aug 7 '12 at 22:28
Markus OrreillyMarkus Orreilly
26113
26113
yeah, I did it, no luck
– PabloG
Aug 7 '12 at 23:05
Doesn't help me
– B T
Jan 14 '16 at 21:54
add a comment |
yeah, I did it, no luck
– PabloG
Aug 7 '12 at 23:05
Doesn't help me
– B T
Jan 14 '16 at 21:54
yeah, I did it, no luck
– PabloG
Aug 7 '12 at 23:05
yeah, I did it, no luck
– PabloG
Aug 7 '12 at 23:05
Doesn't help me
– B T
Jan 14 '16 at 21:54
Doesn't help me
– B T
Jan 14 '16 at 21:54
add a comment |
If sfc
is returning
Windows Resource Protection could not perform the requested operation
I assume you didn't do a full sfc scan? Why don't you try the suggestions here to get sfc /scannow to work again.
If that doesn't help, uploading a full Process Monitor log of what happens when you start up Explorer could help diagnose the problem.
add a comment |
If sfc
is returning
Windows Resource Protection could not perform the requested operation
I assume you didn't do a full sfc scan? Why don't you try the suggestions here to get sfc /scannow to work again.
If that doesn't help, uploading a full Process Monitor log of what happens when you start up Explorer could help diagnose the problem.
add a comment |
If sfc
is returning
Windows Resource Protection could not perform the requested operation
I assume you didn't do a full sfc scan? Why don't you try the suggestions here to get sfc /scannow to work again.
If that doesn't help, uploading a full Process Monitor log of what happens when you start up Explorer could help diagnose the problem.
If sfc
is returning
Windows Resource Protection could not perform the requested operation
I assume you didn't do a full sfc scan? Why don't you try the suggestions here to get sfc /scannow to work again.
If that doesn't help, uploading a full Process Monitor log of what happens when you start up Explorer could help diagnose the problem.
edited Aug 7 '12 at 22:38
Der Hochstapler
68k50230286
68k50230286
answered Aug 7 '12 at 22:22
MatthewSotMatthewSot
2,65232034
2,65232034
add a comment |
add a comment |
I have come here because I had the same problem. Windows File Explorer taking about 20 seconds to start up as well as some other processes with the same delay. The answers didn't help me much, but I found a network drive to not be responding properly. I managed to restore it to operations and voilà everything worked fine again. It turned out, that my %TEMP% was mapped to the non-functioning network drive. That might have played a major role in the startup delay.
add a comment |
I have come here because I had the same problem. Windows File Explorer taking about 20 seconds to start up as well as some other processes with the same delay. The answers didn't help me much, but I found a network drive to not be responding properly. I managed to restore it to operations and voilà everything worked fine again. It turned out, that my %TEMP% was mapped to the non-functioning network drive. That might have played a major role in the startup delay.
add a comment |
I have come here because I had the same problem. Windows File Explorer taking about 20 seconds to start up as well as some other processes with the same delay. The answers didn't help me much, but I found a network drive to not be responding properly. I managed to restore it to operations and voilà everything worked fine again. It turned out, that my %TEMP% was mapped to the non-functioning network drive. That might have played a major role in the startup delay.
I have come here because I had the same problem. Windows File Explorer taking about 20 seconds to start up as well as some other processes with the same delay. The answers didn't help me much, but I found a network drive to not be responding properly. I managed to restore it to operations and voilà everything worked fine again. It turned out, that my %TEMP% was mapped to the non-functioning network drive. That might have played a major role in the startup delay.
answered Feb 11 at 13:28
Jens ManderJens Mander
1
1
add a comment |
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%2f458861%2fwindows-explorer-is-taking-30-seconds-to-start-how-can-i-find-out-why%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
Is this happening with every folder, or only certain ones?
– Markus Orreilly
Aug 7 '12 at 22:29
@MarkusOrreilly: this is happening with every folder I try to open with Explorer. If I navigate the folders with Total Commander -for example- it works fine.
– PabloG
Aug 7 '12 at 23:12