"The file may be write protected" I get this every time I try to render anything from the timeline but minutes before this started happening, everything was okay and I was working with VS.
error code. 15033:10:2
Windows 8.1
VS X7
Nothing has been changed in either VS settings or my computer prior to this problem.
Any help would be greatly appreciated.
Welcome to the forums! However, you need to give us more information before we can even begin to guess at what might be going wrong. First, what format does the video have or is it any video? Where did the video come from? Please right click on a clip in the Video Studio timeline and copy ALL its Properties here or take a screen grab of the Properties box and upload it here as an attachment.
What editing have you done? What filters have you applied, if any?
Have you closed and reopened VS and/or rebooted the computer? Still the same problem?
I, in no way wish to be condescending or negative but VS X7 took almost a month to install correctly using the experience of 3 customer support agents, the last one having to remotely enter my computer and downloading this VSX7-64bit.rar file supposedly, a copy of his own file. Whilst VS X7 still will not allow drag and drop on the timeline I decided to "put up" with this inconvenience.
Now back to the current problem "The file may be write protected"
1) This problem is happening whatever format I attempt to use in both input and output.
2) The video's come from a number of places and even the video's VS X7 has previously rendered are now showing "The file may be write protected" and cannot be rendered.
3) Timeline properties
Microsoft AVI files
24 bits, 1664 x 936, 30 fps
Lower Field First
Xvid MPEG-4 Codec
Interleave audio for every 15 frames
PCM, 48.000 kHz, 16 Bit, Stereo
4) Filters are mainly cut and crossfade although even if I insert a "virgin" video onto the time line, use no filters and attempt to export that video to any format I get "The file may be write protected"
5) Yes I have closed and re-opened VS, I have re-started my computer, I have closed and done a cold start opening only VS but all to no avail, I have not yet tried a re-install.
Can I make clear that I was using VS and edited/rendered 2 video's the 3rd one gave me "The file may be write protected" I reloaded the previous project (already rendered) VS would not render this file and loading the previously rendered file on the timeline would not render in any format.
I hope I have supplied the information requested and I hope you can help me with this issue.
Regards
Misomchi
My guess is that those video clips giving you the message have come from some copy-protected sources, like DVD's or other places that have copy protected them against editing... Al
could you upload a short problem clip to a site such as OneDrive so that we can download it and see if we have the same problem?
The fact that clips that previously rendered correctly now give you the error message indicates that your install is corrupt. I don't know why a Corel support agent would use a "rar" version to install
Perhaps you did not read my previous communication in detail, All files and images will not Render the files/video's, are NOT copy protected neither are the photo images taken by my own camera (Cannon 5) or other free to use images from the internet.
canuck Thanks for your response.
I do not support Microsoft OneDrive due to their personal detail usage and to be perfectly honest. your version of VS will be able to read and render the file as my Daughter has no problem with her version, and, VirtualDub edits the files as does my video converter along with VLC.
I would agree a re-install will be needed but I am loath to do it. If there is a problem with VS X7 Pro V Wndows 8.1 it needs to be resolved and only Corol can do that.
Finally.... The Corel support agent used a "rar" file version because two other agents could not get my "drag and drop" option to work. It now works 50% of the time, so I put up with that.
When this problem has been raised in the fairly distant past (I'm talking 2008 and earlier) a couple of solutions were found -- though I will hastily add that this was not a problem experienced by a lot of users with earlier versions of VS, just a small number.
First, check in windows to make sure that the videos have not been mysteriously changed to write protected -- though in your case, they pretty obviously have not been.
Second, change the system properties of the VS .exe file to always run as Administrator, even though you have Admin privileges on your computer. For some reason or other this seems to have worked for at least one user. (Right click the VS icon on your desktop and select Properties. In the dialogue box which appears go to the Advanced tab and tick 'Run as Administrator'.)
Third, when you go to Share, designate another folder for output rather than the one you have been using. Again, I have no idea why this worked, but it did for a couple of users. One of them was of the opinion that he had passed an unspecified limit on the number of files he could store in the original folder. I know of no such limit, but it seemed to work for him.
I myself have only experienced this problem once, back in 2001 or 2002 when I was using Windows ME, and it turned out to be a driver issue... but I'm afraid I don't remember the details. I currently have both VS X7 and X8 64 bit running on Windows 8.1 64 bit and have no problems at all with either version.
EDIT: another thought... Have you thought about doing a System Restore back to a point where the program was working correctly?
Hi Ken
I spoke to soon. I did a restore and late last night VS started to do some crazy things like hanging, not allowing a file to load and refusing to close down. So I used undo to to put my computer back into the state it was and uninstalled, did a re-install and VS cleanup from the rar files the teck had me download, now all seems normal
Fingers crossed
Regards
Misomchi
"The file may be write protected" I get this every time I try to render anything from the timeline but minutes before this started happening, everything was okay and I was working with VS. 
