Skip to main content
Participant
February 21, 2017
Question

Please fix PE15 windows 10 version

  • February 21, 2017
  • 1 reply
  • 227 views

I just buy pe15 straight in windows store (windows 10 version),  its slightly different with adobe version, in my app information everything like app, data, total usage is 0 bite use space..? confuse.. but it take 4gb my ssd spcace, no update option in help, performance and experience more way way better in adobe version than windows 10 version, by the way its slower my other software to open I don't know why...,its not happen in adobe version (trial),  when I'm open pe15 first than open my vegas pro 14 its take long vegas pro 14 to open, before just like less than 3 second and now take 15 to 20 seconds to open.. why.. please fix this adobe, sorry bad engglish

    This topic has been closed for replies.

    1 reply

    Community Manager
    February 22, 2017

    Hi Wendy,

    Sorry for the inconvenience.

    The installation process is a bit different for windows app store version as compared to retail version and it would be helpful if you can provide more details around:

    1. when you said, "in my app information everything like app, data, total usage is 0 bite use space..?"

    > From where are you checking this information, is it from windows store directly?

    It would be helpful if you can paste a screenshot here.

    2. "No update option available"

    > Although the product name and version number are the same for Windows App Store version and the one purchased from adobe.com, a Windows App Store purchase is a separate build of the application. The Adobe Application Manager (updater) is not installed with Windows App Store versions of Adobe software. Manually downloaded patches from http://www.adobe.com/downloads/updates/ don't update a WAS version. The Windows App Store handles all product updates.

    For more details, please see:

    Purchases through Windows App Store FAQ

    3. Vegas Pro taking too much time to launch

    > Can you please confirm the behavior after rebooting your machine once.

    Thanks,

    Anwesha