Jump to content
You must now use your email address to sign in [click for more info] ×

Search the Community

Showing results for tags 'vssvcc.exe'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.4 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 1 result

  1. A few days ago I updated my second pc, an old and very slow laptop, to Windows 10 1803. I noticed the protected folder feature and left it "as delivered". Today I have tried to update that pc to Affinity 1.6.4.104 and during installation everything appeared to stop (difficult to tell on this pc, it doesn't really have enough umph to pull the skin off a rice pudding). The Notifications box was showing that it had something to tell me and on checking it, it was showing "Unauthorised changes blocked. Controlled folder access blocked C:\Windows\Sy...\VSSVC.exe from making changes to memory". That's really helpful of it, truncating the folder path, but on checking I reckon it's C:\Windows\System32\VSSVC.exe. Simple solution, I turned off folder protection, ran the installation again and everything was fine. So I reckon that MS are shooting themselves in the foot. After all VSSVC is Volume Shadow Copy, maybe something to do with taking a checkpoint before installation? Any second opinions please? Thanks, John
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.