Strange behavior after CDBurning is disabled
Dear all,
While testing Vista CDBurning, I found a strange Explorer behavior...
1. Install Vista Beta2 5384
2. Insert a blank DVD+RW disc.
3. Format the disc.
4. Copy some files and it works well. Close all Explorer windows.
5. Lauch "gpedit.msc". Follow "Administrative Template" -> "Windows Component"
-> "Windows Explorer" and then enable the "Remove CD Burning Features" option.
6. Check the formated disc, now I can not drag & drop, copy, and paste any file via
Explorer.
But I can create new folder, new text files and new bitmap files.
Further more, I can use "copy" command under command line mode to copy files
to the disc.
Can anyone explain this behavior ?
Thanks in advance.
[862 byte] By [
Minway] at [2008-2-2]
Hello Minway!
That is some odd behavior. I have some quick questions about the scenario:
1. In step 3, 'format the disc', do you mean formatting it with a Live UDF filesystem?
2. Have you verified that the content you make with new (the new folders, bitmaps, text files, etc) actually end up on the disc?
3. Have you verified that the content you put on the disc with copy from a command prompt actually ends up on the disc?
Answers to these questions will help me see if I can figure out what is going on here :)
Thanks for you interest in IMAPIv2!
Garrett Jacobson
SDE, Optical Platform Group
Dear Garrett,
Many thanks for you reply.
Here are my answers to your questions:
: 1. In step 3, 'format the disc', do you mean formatting it with a Live UDF filesystem?
Yes. The format dialog looks like the XP harddisk format dialog and I choose the recommended
UDF 2.01 file system.
:2. Have you verified that the content you make with new (the new folders, bitmaps, text files, etc)
:actually end up on the disc?
Yes, I've checked the disc with another XP platform.
:3. Have you verified that the content you put on the disc with copy from a command prompt
:actually ends up on the disc?
Yes, I've also checked the disc with another XP platform.
Thank you for the further information Minway. I will investigate and get back to you when I have additional information!
Garrett Jacobson
SDE, Optical Platform Group
Hi Minway,
Just wanted to reassure you that your request was not overlooked. Garrett will provide an update within a couple weeks.
Sorry about the delay,
Henry Gabryjelski
Hi Henry,
It's good to hear that.
Thank you!
Minway
Hello Minway!
Sorry for the delay in tracking this one down. I was able to reproduce this on the latest RC1 builds and have discussed it with the proper teams.
There is definitely a bug here and I have started the process to get it investigated by the appropriate team. However, after speaking with the Live UDF team and the Shell team, the bug is that drag and dropping files should continue to work even after "disabling CD burning in explorer". The reason for this is that it is a legacy GP settings. In XP, this group policy setting disabled the shell burning extension, so it continue to do just that. The live UDF file system does not depend on the shell burning extension and therefore should continue to work even with this policy restriction in place. This should prevent the "Prepare Disc" dialog box from running when you insert blank media though...
Thank you for your help in discovering this issue! Although I cannot promise that this will get fixed, I will drive the issue internally through the appropriate team and will let you know if I have any updates. If you have any further questions about this issue, don't hesitate to let me know!
thanks,
Garrett Jacobson
SDE, Optical Platform Group
PS. If you really wanted to disable all CD burning, you could try using the "Removable Storage Access" group policy settings (particularly "CD and DVD: Deny write access") at the following location:
Local Computer Policy -> Computer Configuration -> Administrative Templates ->System ->Removable Storage Access
Hello Garrett,
Many thanks for your effort and explanation!
I've understanted and agreed with you.
Hope this issue will be fixed soon.
Thank you.
Best Regards,
Minway
Hello Minway,
Unfortunately, this bug has been resolved for the current release as a Won't-Fix for RTM because it does not have severe enough side effects. A PM for the Shell burning team is looking into a KB article to document the issue and make people aware. Hopefully we can still get this behavior corrected for a future release.
Thank you for your help in finding this discrepancy. Please continue to let us know of any issues you encounter and I will help try and get them resolved!
thanks,
Garrett Jacobson
SDE, Optical Platform Group
Hello Garrett,
Thanks for your information.
I can realize your consideration.
Thank you for your effort in this issue!
