title
Products            Buy            Support Forum            Professional            About            Codec Central
 

Windows 10 updates wipe out Asset configuration

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • chrisletts

    • Sep 2016
    • 7

    Windows 10 updates wipe out Asset configuration

    Happened again. Every time there is a major Windows 10 update, my Asset (release 6) configuration gets wiped out and I have to type in the whole thing again.

    Does anyone know what particular file(s) are the ones affected.
    I am very familiar with most of the Asset files that define e.g. the icons and search keys, and those don't seem to get affected by updates, so why the config ?
    Last edited by chrisletts; August 09, 2017, 11:41 AM.
  • Spoon
    Administrator
    • Apr 2002
    • 44582

    #2
    Re: Windows 10 updates wipe out Asset configuration

    %appdata%\dBpoweramp

    If you type this location into Windows file explorer.
    Spoon
    www.dbpoweramp.com

    Comment

    • chrisletts

      • Sep 2016
      • 7

      #3
      Re: Windows 10 updates wipe out Asset configuration

      Originally posted by Spoon
      %appdata%\dBpoweramp

      If you type this location into Windows file explorer.

      That gives me nothing except a bin file for CD ripping, and a text file with a list of genres !

      Comment

      • mville
        dBpoweramp Guru

        • Dec 2008
        • 4021

        #4
        Re: Windows 10 updates wipe out Asset configuration

        Originally posted by chrisletts
        That gives me nothing except a bin file for CD ripping, and a text file with a list of genres !
        What is your Asset Running Mode, Local Account or Service?

        Comment

        • chrisletts

          • Sep 2016
          • 7

          #5
          Re: Windows 10 updates wipe out Asset configuration

          Originally posted by mville
          What is your Asset Running Mode, Local Account or Service?
          Running as service, so I don't have to go to the office to log on every time I want music !

          Comment

          • mville
            dBpoweramp Guru

            • Dec 2008
            • 4021

            #6
            Re: Windows 10 updates wipe out Asset configuration

            Is your Windows 10, 64-bit?

            Comment

            • chrisletts

              • Sep 2016
              • 7

              #7
              Re: Windows 10 updates wipe out Asset configuration

              Originally posted by mville
              Is your Windows 10, 64-bit?
              yes it is

              Comment

              • mville
                dBpoweramp Guru

                • Dec 2008
                • 4021

                #8
                Re: Windows 10 updates wipe out Asset configuration

                For the Windows OS, Asset UPnP configuration files exist in a umedialibary folder, the location of which varies, depending on the Asset UPnP Running Mode and the OS version.

                If the Asset Running Mode is Local Account, then the umedialibary folder is located here:
                %appdata%\dBpoweramp

                i.e. in the user account's AppData folder (C:\Users\%userprofile%\AppData\Roaming\dBpoweramp ).

                If the Asset Running Mode is Service, then the umedialibary folder is located here, for Windows 64-bit versions:
                C:\Windows\SysWOW64\config\systemprofile\AppData\R oaming\dBpoweramp

                It is very likely, but I am not entirely sure, but if the Asset Running Mode is Service, then the umedialibary folder is located here, for Windows 32-bit versions:
                C:\Windows\system32\config\systemprofile\AppData\R oaming\dBpoweramp

                Perhaps a Windows 32-bit OS user running Asset can confirm this?

                Comment

                • chrisletts

                  • Sep 2016
                  • 7

                  #9
                  Re: Windows 10 updates wipe out Asset configuration

                  Originally posted by mville
                  For the Windows OS, Asset UPnP configuration files exist in a umedialibary folder, the location of which varies, depending on the Asset UPnP Running Mode and the OS version.
                  ....
                  If the Asset Running Mode is Service, then the umedialibary folder is located here, for Windows 64-bit versions:
                  C:\Windows\SysWOW64\config\systemprofile\AppData\R oaming\dBpoweramp
                  ....
                  So do you reckon it will solve the problem to keep a backup copy of AssetUPnPDefinedBrowseTreev6.txt and then when windows wipes it during an update, to reinstate it. (or even the whole folder?)
                  My browse tree is considerably different to the default one.

                  I still can't see why a Windows update would wipe it though !

                  Comment

                  • mville
                    dBpoweramp Guru

                    • Dec 2008
                    • 4021

                    #10
                    Re: Windows 10 updates wipe out Asset configuration

                    Originally posted by chrisletts
                    So do you reckon it will solve the problem to keep a backup copy of AssetUPnPDefinedBrowseTreev6.txt and then when windows wipes it during an update, to reinstate it. (or even the whole folder?)
                    Yes, I always backup the umedialibrary folder.


                    Originally posted by chrisletts
                    I still can't see why a Windows update would wipe it though !
                    Because software companies are idiots and do not test/cater for all scenarios, present company (Illustrate) excluded, of course
                    Last edited by mville; August 14, 2017, 03:32 PM.

                    Comment

                    • Pipa

                      • Feb 2018
                      • 3

                      #11
                      Re: Windows 10 updates wipe out Asset configuration

                      Thanks for the solution!

                      Comment

                      Working...

                      ]]>