Article - 817768 Windows Explorer Stops Responding

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

H
I've run into the problem described in MS knowledgebase Article 817768 Windows Explorer Stops Responding When It Tries to Sort More Than 1 Million Objects on a RAID Controlle

I got the fix from MS and applied it, then I went to modify the registry as it states and is shown below

Click Start, click Run, type regedit, and then click OK.
Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\policies\Explore

On the Edit menu, point to New, and then click DWORD
Type SortMaxItemCount, and then press ENTER.
On the Edit menu, click Modify.
Type Maximum_#, and then click O

I'm a bit confused though as I thought DWord values were 4 bit hex or decimal. I entered the value stated (Maximum_#) but the new attribute still displays 0. I question if this is correct because I'm still experiencing the problem, Explorer hangs and consumes about 98% of the CPU resources although it is a little better. I'm zipping files up to get under 1 million but if I don't do it on a continual basis everytime the server gets over 800,000 files explorer starts to get slow and hang. The files aren't big just numerous as the application generates lots of PDF & RTF files.
 
In said:
Hi
I've run into the problem described in MS knowledgebase Article
817768 Windows Explorer Stops Responding When It Tries to Sort
More Than 1 Million Objects on a RAID Controller

I got the fix from MS and applied it, then I went to modify the
registry as it states and is shown below;

Click Start, click Run, type regedit, and then click OK.
Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\polici
es\Explorer

On the Edit menu, point to New, and then click DWORD.
Type SortMaxItemCount, and then press ENTER.
On the Edit menu, click Modify.
Type Maximum_#, and then click OK


I'm a bit confused though as I thought DWord values were 4 bit hex
or decimal. I entered the value stated (Maximum_#) but the new
attribute still displays 0. I question if this is correct because
I'm still experiencing the problem, Explorer hangs and consumes
about 98% of the CPU resources although it is a little better. I'm
zipping files up to get under 1 million but if I don't do it on a
continual basis everytime the server gets over 800,000 files
explorer starts to get slow and hang. The files aren't big just
numerous as the application generates lots of PDF & RTF files.
Click to expand...

http://support.microsoft.com/default.aspx?scid=kb;en-us;817768
assume would be the "easy" way but you must have a reason not to go
with SP4.

I have no problem entering 2000000 (Decimal) into a DWORD valuename
which results in 001e8480 (Hexidecimal). Not that I advocate that
figure nor understand from the article what values may or may not be
valid.
 
In said:
Actually the system is already at SP4 and I still had to get the fix
Click to expand...

Well thenm, they lie! :-)

The shell32.dll from W2K SP4 is ver
5.0.3700.6705
Patch version listed as
5.0.3700.6697

Hope you get it working as desired.
 
Back
Top