.themepack

dadaneo

.themepack file association removed after jv16 power tools.

jrace

Same thing over here on my win7/32 SP1. : : :

jrace

Hi "dadaneo"

According to my experience "jv16 PT 2012" is in the normal mode of "Clean and fix my Computer" extremely aggressive with file extensions.

See pictures:

Themepack 2.PNG

Themepack 1.PNG

As I said before it happened to me some weeks ago that I killed with "PT" the file association for Win7 theme packs. Luckily I found the corresponding backups and recovered the whole thing.

Since that happening I recovered all backed up file extensions and put them into the ignore list which paid off as a good move. There had been some more extensions which I really need.

So I hope for you that you still have a good backup.

OK, that development was a bit past the limit.

Therefore I don't understand that nobody from the team seems to be caring about this problem.

roberta

Good Day,

I have ran into the same issue after installing jv16 PowerTools 2012 2.1.0.1173 (was using 2011, & thought/hoped it would be "safe" to now use 2012)....

Could someone from Macecraft (Jouni?) Please reply to this thread.....

Thank You,

Best Regards,

Roberta

redseujac

In the meantime you can add ".themepack" and ".theme" to the "Ignore words" option of the Registry Cleaner, or - after running the tool - select the entries and choose "Never show again" in the context menu.

jrace

redseujac wrote
In the meantime you can add ".themepack" and ".theme" to the "Ignore words" option of the Registry Cleaner, or - after running the tool - select the entries and choose "Never show again" in the context menu.

...as I already stated above!

And so far I know, the "meantime" you mention, will last for ever!

redseujac

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

aav

Edited by moderator

... (sentence in foreign language removed. Posts must be posted in English except for the subforum "Product Translation Discussion').

Start->Run->cmd

assoc.theme=themefile

assoc.themepack=themepackfile

jv16

jrace wrote
As I said before it happened to me some weeks ago that I killed with "PT" the file association for Win7 theme packs. Luckily I found the corresponding backups and recovered the whole thing.

So what exactly happened after you removed these registry keys?

jrace

jv16 wrote
jrace wroteAs I said before it happened to me some weeks ago that I killed with "PT" the file association for Win7 theme packs. Luckily I found the corresponding backups and recovered the whole thing.

So what exactly happened after you removed these registry keys?

Actually nothing deadly did happen but when you download a win7 theme from microsoft pages or different the option "Open with..." is not anymore available. That might scare you to death. but you could still download the themefile and install it by doubleclicking.

So not really deadly but anyway no good to bring up registry items for deletion that are still needed for the system.

Same thing with ".qbb" extension, these are backupfiles of the Office Software "QuickBooks" (Lexware). In that case if you doubleclick a .qbb-file in windows explorer it would not find the corresponding program (QuickBooks) to open it!

And as I sayd in the PT Lite 2013 beta forum I did not check all the other extensions (~ 120) cause I'm not a extension specialist!

jv16

jrace wrote

Actually nothing deadly did happen but when you download a win7 theme from microsoft pages or different the option "Open with..." is not anymore available. That might scare you to death. but you could still download the themefile and install it by doubleclicking.

So not really deadly but anyway no good to bring up registry items for deletion that are still needed for the system.

Same thing with ".qbb" extension, these are backupfiles of the Office Software "QuickBooks" (Lexware). In that case if you doubleclick a .qbb-file in windows explorer it would not find the corresponding program (QuickBooks) to open it!

And as I sayd in the PT Lite 2013 beta forum I did not check all the other extensions (~ 120) cause I'm not a extension specialist!

As reported by Hukka, the issue relating to .themepack is now fixed and the fix will be available in the next released version. If you wish to fix the issue right now, just add the specific file extension names to the ignore list of the Registry Cleaner feature, or to the Global Ignore List (in Settings).

Same applies to the .qbb extension as well.

jrace

jv16 wrote
As reported by Hukka, the issue relating to .themepack is now fixed and the fix will be available in the next released version. If you wish to fix the issue right now, just add the specific file extension names to the ignore list of the Registry Cleaner feature, or to the Global Ignore List (in Settings).

Same applies to the .qbb extension as well.

@ jv16:

So far so god, but after this experience I am a little anxious to kill all the rest of about 120 extensions.

Actually I think it's not a good solution to put just these into the ignore list, kill the rest and just sit there and wait for the next "desaster" coming up. Because that happenes everytime when you just cleaned up the backups or you just don't even recognise the desater emerges from a file extension which you killed months ago with "jv16 PwereTools".

I have to admit, I don't understand very much about coding or file extensions. But I must say in the long term it should be better to change the algorithm to discover a really not used extension. Otherwise you produce within days may be 100000 or more truncated Windows Systems from people who do understand about these things even less than I do.

The lucky thing about it is: they don't even know it was "jv16 PowerTools".