Windows XP Hotfix KB821557 - Breaks desktop shortcut to cdrom devices

  • Thread starter Thread starter Shortbigg
  • Start date Start date
S

Shortbigg

I have found that the Windows XP Hotfix KB821557 Security Update
causes my desktop shortcuts to my cdrom devices to fail. After
installing the update on my Windows XP Pro installation, the shortcuts
give an error that says the "device letter" has been moved or changed
and the shortcut is no longer valid. Then it gives the option to
either cancel or delete the shortcut. Because of this i can no longer
browse or eject the drive using the shortcut.

Upon removal of hotfix KB821557 the behavior of the shortcut goes back
to normal.

Is there a possible fix to this problem?

Thanks
Maurice Smith
 
Reported on the 18th, MS is looking into it as of the 18th.

--
Just my 2¢ worth,
Jeff
__________in response to__________
| I have found that the Windows XP Hotfix KB821557 Security Update
| causes my desktop shortcuts to my cdrom devices to fail. After
| installing the update on my Windows XP Pro installation, the shortcuts
| give an error that says the "device letter" has been moved or changed
| and the shortcut is no longer valid. Then it gives the option to
| either cancel or delete the shortcut. Because of this i can no longer
| browse or eject the drive using the shortcut.
|
| Upon removal of hotfix KB821557 the behavior of the shortcut goes back
| to normal.
|
| Is there a possible fix to this problem?
|
| Thanks
| Maurice Smith
 
Shortbigg said:
I have found that the Windows XP Hotfix KB821557 Security Update
causes my desktop shortcuts to my cdrom devices to fail. After
installing the update on my Windows XP Pro installation, the shortcuts
give an error that says the "device letter" has been moved or changed
and the shortcut is no longer valid. Then it gives the option to
either cancel or delete the shortcut. Because of this i can no longer
browse or eject the drive using the shortcut.

Upon removal of hotfix KB821557 the behavior of the shortcut goes back
to normal.

Is there a possible fix to this problem?

Thanks
Maurice Smith
Click to expand...

Hello Maurice !!
It's a rarity to have 2 of us Maurices at the same place. <g>

Would you please provide some details. It would help to know & could lead to pinpoint the cause (beyond just this update): At the time this "fix" was installing, did you have other open programs or your stuff running? Is there an antivirus program; if so which one?

Did you have Service Pack 1 already installed?
Did you respond YES to reboot the system right after completion of this item?
Both of those conditions are a must.

The only file updated by this is Shell32.dll. See how *many* you have & what version number is the 1 in your System32 folder?

How many CDRom devices do you have & name/make/model & what drives are they?
Did you also look in Windows Explorer to look at CD devices when this problem occurred?
Are they standard IDE devices or SCSI?

You & Mrtee's problems are the serious ones that I have seen.
 
Hello Maurice !!
It's a rarity to have 2 of us Maurices at the same place. <g>

Would you please provide some details. It would help to know & could lead to pinpoint the cause (beyond just this update): At the time this "fix" was installing, did you have other open programs or your stuff running? Is there an antivirus program; if so which one?

Did you have Service Pack 1 already installed?
Click to expand...

Yes. However, immediately after installing SP1 I checked and the
problem was not there. It did not appear until after the installation
of the mentioned Hotfix, KB821557.
Did you respond YES to reboot the system right after completion of this item?
Yes.

Both of those conditions are a must.

The only file updated by this is Shell32.dll. See how *many* you have & what version number is the 1 in your System32 folder?
Click to expand...

There is only one version of Shell32.dll in the System32 folder. The
version number is 6.0.2800.1233. (Be advised this information is now
coming from a restored installation of Windows XP Home Edition on the
same computer. After seeing what this was doing in my XP Pro version,
I decided to use the original restore disk on this machine and see if
the issue could be recreated. It exhibits the same behavior as the XP
Pro version.)
How many CDRom devices do you have & name/make/model & what drives are they?
Click to expand...

I have two CDR devices installed and the problem exists for either
one. One is a Lite-On DVD Rom LTD 163 and the other is a Phillips
CDRW2412A. Be advised the shortcut works fine upon the removal of the
hotfix and ceases to work upon reinstallation for both drives.
Did you also look in Windows Explorer to look at CD devices when this problem occurred?
Click to expand...

I didnt not look in Windows Explorer, however I did check My Computer
and both drives can be ejected with the right click context menu eject
item. This is consistent both while the hotfix is installed and
uninstalled as well. Only shortcuts to the drive seem to be affected.
Are they standard IDE devices or SCSI?
Click to expand...

Standard IDE devices.
You & Mrtee's problems are the serious ones that I have seen.
Click to expand...

Hope this information is useful. I realize this isn't a "critical"
issue, but it is an annoyance to be required to open "Explorer" or "My
Computer to access these drives each time they need to be opened or
ejected.

Thanks for your concern,
Maurice Smith
 
Trying to flag this for Jonathan Woodard.

Maurice, I wonder if you had a chance to look at the properties of the
shortcut? to see if drive letters or something got clobbered?
--
Maurice N
MVP Windows - Shell / User>>

I had the same issues, as noted by others in the Update newsgroup - see
thread titled
"Re: 821557 & 823980 critical update problem" going back to the 18th or 19th
of this month. This is not unique to Maurice. I created shortcuts to all my
drives, got same error messages, but found that using My Computer or
Explorer to open and browse the drives worked fine for me too. Microsoft
screwed up the patch.

Georgia
 
Trying to flag this for Jonathan Woodard.

Maurice, I wonder if you had a chance to look at the properties of the shortcut? to see if drive letters or something got clobbered?
Click to expand...

The shortcuts point correctly to the devices both before and after the
hotfix. Removing the hotfix restores the correct behavior using the
same shortcuts that are dsyfunctional with the hotfix installed.

Maurice Smith
 
Maurice,

I installed 821557 and have the same problem as you. However, if I fill in
the "Start in" parameter of the shortcut with the drive letter (it normally
is blank), it will work. Do you see this?

Bruce
 
Oh, and BTW, when I clicked to reboot to finish the installation, XP
blue-screened on me. Not a very healthy thing you want to see when
installing an MS patch <g>. I've uninstalled 821557, needless to say.
 
Maurice,

I installed 821557 and have the same problem as you. However, if I fill in
the "Start in" parameter of the shortcut with the drive letter (it normally
is blank), it will work. Do you see this?

Bruce
Click to expand...


I gave this a try to no avail. When I fill in the "Start in"
information and apply it, an error dialog box comes up that reads:

"The folder 'F:\' specified in the Start In box is not valid. Make
sure that the folder exists and that the path is correct."

Perhaps a fix will come down the line on this. I have inquired with a
couple of associates and one has the problem, while the other doesn't.
This makes it harder to pin down I guess.

Thanks for the input,
Maurice Smith
 
Shortbigg said:
I gave this a try to no avail. When I fill in the "Start in"
information and apply it, an error dialog box comes up that reads:

"The folder 'F:\' specified in the Start In box is not valid. Make
sure that the folder exists and that the path is correct."

Perhaps a fix will come down the line on this. I have inquired with a
couple of associates and one has the problem, while the other doesn't.
This makes it harder to pin down I guess.

Thanks for the input,
Maurice Smith>>
Click to expand...

Same here - as I was testing this method to see if it worked for me. I get
the same error no matter how I fill in the boxes in the shortcut properties.
Georgia
 
Back
Top