@@luthandokhuzwayo4489 If you import the exported video and then export again you might loose some quality (mainly depending on the codec you use). but if you use the same codec, bitrate, resolution etc. the difference is very very small.
I just needed to restart Premiere. Thank you for telling me the obvious in a calm voice. I so instantly frustrated when I kept getting the error after spending hours on a project, I really need that.
Omg, after literal hours of trouble shooting, this finally helped! Apparently creating a new sequence and copy/pasting was the cure! It's ridiculous to think that such a simple solution could halted my progress so much. Thank you so much for the video!
Hey guys, if you're trying to render your timeline for preview and getting this error, a fix I've discovered on my Windows device with an NVIDIA GPU is to go into sequence settings and change your 'Preview File Format' to 'QuickTime'. I hope this helps as well.
I have to give you huge credit for what you have done and are doing now. Being forced to change your entire, established brand and recreate your library is a monumental undertaking. You Sir are a true dedicated, talented, professional. 😊
@@Storysium Were you forced to change the name of your YT channel (Orange83)? If so, would you mind sharing what happened? Just a fellow content creator (in a completely different lane), looking to minimize potential heartache/headache. PS - I just watched your video about you stepping away from the channel. Just wanted to say thank you for your contribution to this platform. I've learned a great deal from you. Hope you're able to reignite a fire for video, filming your own projects. You will do well, whatever you decide to do. Wishing you all the best.
The other possible resolution I often use is deleting the preview (.PRV) files where the Premiere project file is located. Premiere Pro creates cached/accelerator files to speed up your workflow but sometimes these files become corrupt or orphaned files. 1. Close your project. 2. Go to your Premiere Pro file location. 3. Search for .PRV 4. (When the Search is done) Select all and delete all the .prv files. 5. Re-open your project and then try exporting again.
Finding Timestamp helped me, I had repeated effects on clips back to back and that was the issue. when I placed it on an adjustment layer it helped the situation and allowed me to export. THANK YOU!!!
Thank you for your help. Disabling the GPU worked. Had I not bumped into this video, I would have started from scratch and frustratingly get the same error again. Subscribing!
I have found one method to Render the heavy sequences ..it is by after completing your project select all except with the adjustment layers/ text that uses blending modes and nest them all..this will speed the rendering and export also.. 💯
Storysium, you are a freaking genius. I have a Mac and nothing in the threads on Adobe's solutions areas for issues worked except for one of your suggestions here (finally LOL). It was the suggestion you had to 'mark in and mark out' an area of a project. 99% of my vids are all audio related so all i needed was the MP4 format to publish the video on YT. Your suggestion worked! So my advice to folks who are in the same position as I am: When you know you are doing a project to be published to YT, do a 'mark in and mark out' of your project and export into MP4. I had no solution and this worked great for me. Thanks Storysium! Now I can keep doing my interviews 😊
Restarting my system worked for me. It was getting glitchy with a lower third, and needed updating. Once updated, it kept doing it, so i closed everything and restarted. Thank you so much. Oh and it was doing this on Render in and out, not on Render/Export. You Rock!!!
In my case the timestamp that was displayed in the error, I adjusted the transition between 2 clips. Thanks for saving my time, I wasted 3 hours in trying to fix, clearning the temp, restarting etc.
GPU running out memory during export. happens with effects and resizing 4k footage. Use 'render and replace' on affected clips. Set memory management to 'memory' instead of performance. in my case also turning off hardware decode/encode helps sometimes.
I solved this problem rather unconventionally, after trying all your solutions on my 1 hour 36 minutes long video, I came up with a cunning plan. I exported it as 15 minutes long individual videos (by looking at the exact point in time). So I basically had 6 parts of perfectly exported videos. I opened a new project, put them all together perfectly, and exported again, it worked like a breeze! ❤️
I actually came down here to appreciate the user recommendation that you added as the last option IT WORKED FOR ME AND IT'S SIMPLE! it should actually be the first.
nothing except render by media encoder, every other fails. But media encoder doing it a little bit longer 6 min vs 17 min. (with cuda on) I don't know why it happend, yesterday everything was ok..
worked for me..I just needed to restart Premiere & also clear some space on my hard drive . Thank you for telling these solutions..never thought a simple solution will solve it, Cheers to you
your a legend mate, nothing was working... Exporting through the media encoder saved me... Working on a big paid project and I would be ruined if I couldn't get his footage out. Thankyou
this was honestly the most frustrating issue and nothing was working, eventually i got to step 6 where you select software encoder rather than hardware encoder and it worked (but took much longer)!!!!!!!!!!! thank you SO much for your help :)
Just a quick tip that I am going to spam/comment in some video-tuttorials with this subject : I was stuck and frustrated with the ccp-814 error for many days. Then I started exporting my project in smaller sections (part1 part 2 part 3) hoping to connect it on a different edit session. And then BAM! One of the fragments/parts got the same error mesage. Then it became easy to detect the problem. It seems that adobe premiere has some kind of "sensitivity" for audio that is left even on a muted track. This was bringing the whole project to collapse. When I resolved this, everything went smooth like before! Try it.
In my case, I had applied an Adjustment layer with lumetri color effect. Little did I know that the track benethe had a dip to black effect and lumetricolor wasn’t able to render that small portion hence the error came. Hence removed the dip to black from the clip below to the adjustment layer and solved the issue (I had CUDA on the whole time)
I tried all the possible solution but one of the new sequence trick work for me . It is simple just make a new sequence and copy all of your project and paste to the new sequence and export. Thank you Admin ❤️
Dear "Orange" ( :-D ) thank you so much!!! Maybe for years now I was suffering getting the only way I knew (direct export) and having so much pain. 9 from 10 tryouts failed. Now, with your suggestion to get it in the "render queue" of the Media encoder finally it works 100%! Really , I cannot believe. You are the best! Thank you again for your incredible work!
Nearly had a heart attack this morning! How infuriating!! I run an old Mac Pro with an RX 580 8Gb GPU. Disabling CUDA solved my issue. Seem to remember it solving this issue a few years ago, too. Very helpful guide. A big Thank you from Kris' Sweets! =)
Had this issue several times because of the warp stabilizer not being rendered inside of a nested transition. It would render on the clip, but not on the nested transition portion - I just had to remove the warp from the 15 frames of transition and adjust the scaling to match the stabilized clip before it.
BIG THANK YOU! Copying everything from the project in new one make the difference and repair the problem , I exported right after I made the new project! THANK YOUUUU
Thanks for sharing the solutions, today only i got the error message while exporting my video. didn’t knew why it was showing. i was trying to export a preview copy only, but it was not working. then u unticked the “ use previews” option on the export window and used match source option and then it worked .
Best video of all the ones that cover this error. I switched to Media Encoder before watching this and it worked for me. But ME is slower even with hardware acceleration compared to PPro
i always export to my old 10 year old SSD and i get the error a lot. now i bought a new fast SSD and i already got 10 videos in my channel with 0 errors.
Saving and restarting my computer actually made it work no problems. Kind of silly how I always seem to forget turning it off and on again works so well.
thank you so much . changing from gpu to software only solved my problem.. my only question is shoud i stay at software only. or should i try exporting other project using gpu
The error message says the exact time the error occurs. I removed the "Dip to White" transition in this particular shot, reinserted, and voilá! Thank you so much.
I really appreciate ya man ,I see u are working so hard to re-create content... if there's any chance I'll support 😄 really appreciate your hard work 👏
Another possible solution. Pre-Render In to Out in sections. I was having compiling errors when pre rendering my sequence using Render In and Out. If I turned a few layers off, Pre-render in and out, then turn on the last few layers and do it again, i didnt get errors. Hope this helps
basically all of this was unapplicable to me, i was already doing everything, but instead of using cuda, i switched it to gpu acceleartion and that fixed it i believe.
A) I love you video's, amazing stuff. B) I made a cool vid using your "paper stack transition" (so cool by the way), and every time PrePro got to the first "paper stack" it failed because of the effects. So after 2 hours I tried all 9 of your suggestions here, and NONE of them worked. So then I did this...C) I nested the whole project and created a dynamic link to After Effects, then there I simply added to the AE render que and rendered it from there, then Re-Rendered it in PrePro, and that finally worked. Just a thought. Thanks again.
Im sure this video will help me! Yesterday I received the error and the reboot helped me but its good to know another suggestions. Thanks for your help!! Regards!
I've tried each of these steps and while they usually work, they unfortunately have not this time🙃 Each and every time I get the export error message at a different random point in the video, have been trying to export this for 3 days straight now😑 I do have to say thought this is the best video on the topic by far and is a 99% solution
Another version of this problem: This happened to me cause of a faulty/wrong type of usb-c chord for my SSD which made it disconnect (or at least loose contact with the footage at random. Switched it for a proper one and the problem is gone! Great video though. You're a UA-cam Superhero!
Thanks to your video, I just solved mine. I was given the time stamp in the error message but the time stamp didn't match the time stamp on my timeline. However, it also mentioned the effect (Stabilizer) in the error message and so I disabled the effect and the rendering did complete.
OMG TYSM. I was editing a pretty big video and it was due but I came upon this error and i didn't know what to do. The very simple Retry, Reboot method worked perfectly for me and it uploaded successfully. You have my many thanks.
![I Replaced ALL my ADOBE APPS with these [free or cheaper] Alternatives!](http://i.ytimg.com/vi/5EfqHg49kMk/mqdefault.jpg)
Another possible workaround: Try to export increments and then take those parts and piece them back together and export as a whole.
If you export footage more than once, don't you loose quality?
@@luthandokhuzwayo4489 If you import the exported video and then export again you might loose some quality (mainly depending on the codec you use). but if you use the same codec, bitrate, resolution etc. the difference is very very small.
I just needed to restart Premiere. Thank you for telling me the obvious in a calm voice. I so instantly frustrated when I kept getting the error after spending hours on a project, I really need that.
Glad I could help! Thanks for sharing!
Same here restart did the trick
@@Storysium thankyou
Omg, after literal hours of trouble shooting, this finally helped! Apparently creating a new sequence and copy/pasting was the cure! It's ridiculous to think that such a simple solution could halted my progress so much. Thank you so much for the video!
Yeah, that saved my life too! AHAHAHA
This also worked. Just make a subsequence. Adobe PP is glitchy like that sometimes.
THANK YOU!
Hey guys, if you're trying to render your timeline for preview and getting this error, a fix I've discovered on my Windows device with an NVIDIA GPU is to go into sequence settings and change your 'Preview File Format' to 'QuickTime'. I hope this helps as well.
thank you Love you so much :D :D :D :D: :D :D :D Love Love Love
worked for me!
It worked thank you, but why? 🤔
@@vhadianv It has something to do with your GPU and Drivers. QuickTime is a light and popular codec so it plays with almost everything flawlessly.
I have to give you huge credit for what you have done and are doing now. Being forced to change your entire, established brand and recreate your library is a monumental undertaking.
You Sir are a true dedicated, talented, professional. 😊
Thank you very much ❤
Being forced to change?
I always wondered why the name of this channel changed.
Do you happen to know what caused this?
@@Storysium Were you forced to change the name of your YT channel (Orange83)? If so, would you mind sharing what happened?
Just a fellow content creator (in a completely different lane), looking to minimize potential heartache/headache.
PS - I just watched your video about you stepping away from the channel. Just wanted to say thank you for your contribution to this platform. I've learned a great deal from you.
Hope you're able to reignite a fire for video, filming your own projects. You will do well, whatever you decide to do. Wishing you all the best.
Worked on a project for a week now unable to export even after using every single tactic present on youtube 😢
The other possible resolution I often use is deleting the preview (.PRV) files where the Premiere project file is located. Premiere Pro creates cached/accelerator files to speed up your workflow but sometimes these files become corrupt or orphaned files.
1. Close your project.
2. Go to your Premiere Pro file location.
3. Search for .PRV
4. (When the Search is done) Select all and delete all the .prv files.
5. Re-open your project and then try exporting again.
man i was sweatin cos nothing worked then the sequence did and god. my whole night's work is finally able to be exported, you da goat.
Thank you big time! After a million export attempts, export with NVEC worked, can’t thank you enough for this!!!
Finding Timestamp helped me, I had repeated effects on clips back to back and that was the issue. when I placed it on an adjustment layer it helped the situation and allowed me to export. THANK YOU!!!
Thanks for sharing!
ahhh blessings to you, I just needed to free up space was my fix had so many past raw videos (gbs in size) just sitting around still
Thank you for your help. Disabling the GPU worked. Had I not bumped into this video, I would have started from scratch and frustratingly get the same error again. Subscribing!
Glad it helped. Thanks for sharing.
I have found one method to Render the heavy sequences ..it is by after completing your project select all except with the adjustment layers/ text that uses blending modes and nest them all..this will speed the rendering and export also.. 💯
Storysium, you are a freaking genius. I have a Mac and nothing in the threads on Adobe's solutions areas for issues worked except for one of your suggestions here (finally LOL). It was the suggestion you had to 'mark in and mark out' an area of a project. 99% of my vids are all audio related so all i needed was the MP4 format to publish the video on YT. Your suggestion worked! So my advice to folks who are in the same position as I am: When you know you are doing a project to be published to YT, do a 'mark in and mark out' of your project and export into MP4. I had no solution and this worked great for me. Thanks Storysium! Now I can keep doing my interviews 😊
Awesome!! thanks for coming back and sharing your solution.
The solution with the sequence change worked, thank you! :)
Restarting my system worked for me. It was getting glitchy with a lower third, and needed updating. Once updated, it kept doing it, so i closed everything and restarted. Thank you so much. Oh and it was doing this on Render in and out, not on Render/Export. You Rock!!!
In my case the timestamp that was displayed in the error, I adjusted the transition between 2 clips. Thanks for saving my time, I wasted 3 hours in trying to fix, clearning the temp, restarting etc.
Glad it helped! thanks for sharing
Fixed my issue by extending the intro ticker I designed to the start of the video. Thank you
GPU running out memory during export. happens with effects and resizing 4k footage. Use 'render and replace' on affected clips. Set memory management to 'memory' instead of performance. in my case also turning off hardware decode/encode helps sometimes.
Thanks for sharing!!
I solved this problem rather unconventionally, after trying all your solutions on my 1 hour 36 minutes long video, I came up with a cunning plan. I exported it as 15 minutes long individual videos (by looking at the exact point in time). So I basically had 6 parts of perfectly exported videos.
I opened a new project, put them all together perfectly, and exported again, it worked like a breeze! ❤️
Good solution, thanks for sharing.
works for me ty
I actually came down here to appreciate the user recommendation that you added as the last option IT WORKED FOR ME AND IT'S SIMPLE! it should actually be the first.
finally worked after pasting everything to a new project and found and adjusted the clip according to the error timecode...thank you!
Also, its awesome that you didnt give up and quit, but instead, got busy remaking your videos and still making new ones! You are awesome!
Thank you!! 😊❤
@@Storysium absolutely, thanks for all the work that goes into this
The 3rd solution worked for me 02:19 - Export with Media Encoder
Thanks for the tutorial!
Glad it helped! Thanks for coming back and letting us know!
First tip immediately worked for me. Thanks homie! You got that like.
Glad to hear it, thanks for coming back to let us know.
nothing except render by media encoder, every other fails. But media encoder doing it a little bit longer 6 min vs 17 min. (with cuda on) I don't know why it happend, yesterday everything was ok..
I have same problem. How did you solve it?
worked for me..I just needed to restart Premiere & also clear some space on my hard drive . Thank you for telling these solutions..never thought a simple solution will solve it, Cheers to you
Thanks for sharing!
your a legend mate, nothing was working... Exporting through the media encoder saved me... Working on a big paid project and I would be ruined if I couldn't get his footage out. Thankyou
Awesome, thanks for sharing :)
Disabling CUDA worked for me! Thank you so much you have saved my day!
Glad it helped! thanks for sharing.
The media encoder option worked for me, thanks much!!! Saved me a ton of time.
Great to hear! Thanks for sharing your solution
#8 did the trick... Copy and paste everything solved ALL the issues that were happening before... THANKS!
this was honestly the most frustrating issue and nothing was working, eventually i got to step 6 where you select software encoder rather than hardware encoder and it worked (but took much longer)!!!!!!!!!!! thank you SO much for your help :)
Thanks for sharing!
This solved my problem too. Even deleting the suspect file didn't work for me.
I was so helpful. my problem was solved by creating a new sequence and copying files to it. Thank you so much.
I fixed the problem with method 1: retry&reboot. your content is very helpful and you saved my channel
I was going to stop the tutorial bcz noothing was working then finally something worked for me at the end, THANKS IT WORKED
Creating new project and importing the older is solution for me. Thank you so much
8 Helps Bro! Thanks!
Glad to hear it! Thanks for sharing
awesome video, thank you for compiling these solutions! also your voice is nice to listen to.
So nice of you!
Just a quick tip that I am going to spam/comment in some video-tuttorials with this subject : I was stuck and frustrated with the ccp-814 error for many days. Then I started exporting my project in smaller sections (part1 part 2 part 3) hoping to connect it on a different edit session. And then BAM! One of the fragments/parts got the same error mesage. Then it became easy to detect the problem. It seems that adobe premiere has some kind of "sensitivity" for audio that is left even on a muted track. This was bringing the whole project to collapse. When I resolved this, everything went smooth like before! Try it.
Love you Man, I wasted lots time due to this error and now its fixed...
In my case, I had applied an Adjustment layer with lumetri color effect. Little did I know that the track benethe had a dip to black effect and lumetricolor wasn’t able to render that small portion hence the error came. Hence removed the dip to black from the clip below to the adjustment layer and solved the issue (I had CUDA on the whole time)
Thanks for making this video, this error has been killing by ability to get client work completed on time
Hopefully it's solved now for you
Thanks as always 😊 and A Very Happy New year 😃 🎉 @Storysium
❤
@@Storysium 😃
2nd solution worked for me. Thanks a lot for helping
This has never happened to me before when exporting videos, but thank you for this video! I finally managed to export with tip #6… 👍🏽👍🏽👍🏽
I saw this video only after I got error in compiling H264 movie. Exporting through Adobe media encoder trick worked for me. Thank you.
Thanks for sharing! That really helps us all.
0:53 Solved my Problem, Thanks Buddy 😍
I tried all the possible solution but one of the new sequence trick work for me . It is simple just make a new sequence and copy all of your project and paste to the new sequence and export. Thank you Admin ❤️
Thanks for sharing!
Hey man hats off to you... Your 4th trick helped me.. It took time but the video got rendered... Keep growing..
Glad it helped, thanks for sharing :)
For me what worked was to copy sequence, then paste into a new sequence. Thanks !!
Dear "Orange" ( :-D ) thank you so much!!! Maybe for years now I was suffering getting the only way I knew (direct export) and having so much pain. 9 from 10 tryouts failed. Now, with your suggestion to get it in the "render queue" of the Media encoder finally it works 100%! Really , I cannot believe. You are the best! Thank you again for your incredible work!
Awesome!! Thanks for sharing. 🟠
Nearly had a heart attack this morning! How infuriating!! I run an old Mac Pro with an RX 580 8Gb GPU. Disabling CUDA solved my issue. Seem to remember it solving this issue a few years ago, too. Very helpful guide. A big Thank you from Kris' Sweets! =)
Excellent, thanks for sharing.
Thanks very much for the help
Changing the Editing mode worked for me, thanks.
Had this issue several times because of the warp stabilizer not being rendered inside of a nested transition. It would render on the clip, but not on the nested transition portion - I just had to remove the warp from the 15 frames of transition and adjust the scaling to match the stabilized clip before it.
Thank you for helping me out. I really thought i wasted a whole day on a video which i cannot export. Fr tho u saved my effort. Thank u
BIG THANK YOU! Copying everything from the project in new one make the difference and repair the problem , I exported right after I made the new project! THANK YOUUUU
Thanks for sharing the solutions, today only i got the error message while exporting my video. didn’t knew why it was showing. i was trying to export a preview copy only, but it was not working. then u unticked the “ use previews” option on the export window and used match source option and then it worked .
Thanks for sharing!!👍
@@Storysium 😊😊
Best video of all the ones that cover this error. I switched to Media Encoder before watching this and it worked for me. But ME is slower even with hardware acceleration compared to PPro
Saved and closed. Then re-opened. it worked. Thank you
Thank you so much. Creating a new sequence did the trick for me.
Preferences reset and new project export worked for me.. thank you so much
Glad it helped, thanks for sharing.
i always export to my old 10 year old SSD and i get the error a lot. now i bought a new fast SSD and i already got 10 videos in my channel with 0 errors.
As always clear english and concentrated content. And shift to Storysium channel name is very successful I suppose. Good luck. Thanks a lot.
Thank you very much!!👍❤
Wow! What a timing! Was searching for a solution as I was getting error while exporting a video today. Thanks
Awesome. Please let us know what fixed your error.
Saving and restarting my computer actually made it work no problems. Kind of silly how I always seem to forget turning it off and on again works so well.
Tysm! The disable cuda one worked for me 😁😁
my concerned was solved with the very first solution you have told in this video. Thank you very much.
Glad to hear that, thanks for sharing
Man, Thank You so much. you save my college assignment, btw the first solution work for me.
Glad it helped! Thanks for sharing.
#1 worked for me! Thank you so much!
thank you so much . changing from gpu to software only solved my problem.. my only question is shoud i stay at software only. or should i try exporting other project using gpu
The error message says the exact time the error occurs. I removed the "Dip to White" transition in this particular shot, reinserted, and voilá! Thank you so much.
Nice one! thanks for sharing
Thanks!!!! That last one about changing the sequence settings save me
Thanks pal, I could solve it by installing Media Encoder. I exported media without any issues. Thanks again for your informative video.
Using Media encoder worked for me! Thank you so much!!
Awesome. Thanks for sharing
I really appreciate ya man ,I see u are working so hard to re-create content... if there's any chance I'll support 😄 really appreciate your hard work 👏
thank you so much, importing my video fixed the problem. I was getting so stressed but thanks to you my vid was exported succesfully
Glad it helped! Thanks for sharing
extending something a few frames did somehow work for me, thanks man
Media Encoder helped. Thank you so much!
Creating a new project worked for me. Thank you!
Another possible solution. Pre-Render In to Out in sections. I was having compiling errors when pre rendering my sequence using Render In and Out. If I turned a few layers off, Pre-render in and out, then turn on the last few layers and do it again, i didnt get errors. Hope this helps
basically all of this was unapplicable to me, i was already doing everything, but instead of using cuda, i switched it to gpu acceleartion and that fixed it i believe.
This worked. Thank you!
I did that but it completely remove the rendering bars so idk if it is actually renderable
Thank you sir! Disabling CUDA worked for me!
A) I love you video's, amazing stuff. B) I made a cool vid using your "paper stack transition" (so cool by the way), and every time PrePro got to the first "paper stack" it failed because of the effects. So after 2 hours I tried all 9 of your suggestions here, and NONE of them worked. So then I did this...C) I nested the whole project and created a dynamic link to After Effects, then there I simply added to the AE render que and rendered it from there, then Re-Rendered it in PrePro, and that finally worked. Just a thought. Thanks again.
Awesome, thanks for the compliments and thanks for sharing your solution!
the restart one was so helpful, thank you so much
Media encoder seemed to fix it for me! Thank you!
I tried a new sequence and it worked, thanks🙏🏾
Im sure this video will help me! Yesterday I received the error and the reboot helped me but its good to know another suggestions. Thanks for your help!! Regards!
My render error got fixed once after restarting the PC. Thank you 😊
I've tried each of these steps and while they usually work, they unfortunately have not this time🙃
Each and every time I get the export error message at a different random point in the video, have been trying to export this for 3 days straight now😑
I do have to say thought this is the best video on the topic by far and is a 99% solution
Is it sorted now?
I'm having the exact same issue. Did you ever get it resolved??
Unfortunately still having the same problems😢
no. 8 helps finally!!! thank you so much storysium
Perfect! Thanks for sharing
Another version of this problem: This happened to me cause of a faulty/wrong type of usb-c chord for my SSD which made it disconnect (or at least loose contact with the footage at random. Switched it for a proper one and the problem is gone!
Great video though. You're a UA-cam Superhero!
Thanks for sharing! good tip ;)
#2 helped me ! Found the point where the video wasn’t rendering and just extended that clip a few seconds. Error was fixed !
Thanks so much... Opening new project helped me ❤
Thanks to your video, I just solved mine. I was given the time stamp in the error message but the time stamp didn't match the time stamp on my timeline. However, it also mentioned the effect (Stabilizer) in the error message and so I disabled the effect and the rendering did complete.
Thanks for this valuable tutorial. My fix was rendering in segments, it worked perfectly fine :)
You as always have amazing content and help . Thanks Orange 83 , oh I mean Storysium !
Thank you too! :)
Thank you very helpful!
OMG TYSM. I was editing a pretty big video and it was due but I came upon this error and i didn't know what to do. The very simple Retry, Reboot method worked perfectly for me and it uploaded successfully. You have my many thanks.
I can't believe restarting my computer worked!! Thank you!
Glad it helped! thanks for sharing
@@Storysium After it worked, another error popped up. The fix was to change from Hardware to Software. Easy!!