Disable "FLEXnet Licensing Service"
Pierre--
-
mikhaddo Posted messages 1 Status Member -
mikhaddo Posted messages 1 Status Member -
Hello !!
How are you on this strike day? :D !
I have a quick question about Vista, how can I disable the "FLEXnet Licensing Service" or the "registry key"?
Thanks for your help right away :) !
How are you on this strike day? :D !
I have a quick question about Vista, how can I disable the "FLEXnet Licensing Service" or the "registry key"?
Thanks for your help right away :) !
Configuration: Windows XP Firefox 3.0.5
8 answers
Hi,
So I found my FLEXnet Licensing Service in my system configuration.
- Press Ctrl+Shift+Esc
- Click on the "New task" button
- Type "msconfig"
- Go to the "Services" tab, and it should be in the list
- Uncheck the box, "Apply" and that's it
However, I don't know what this thing is ... if someone could shed some light on it for me.
So I found my FLEXnet Licensing Service in my system configuration.
- Press Ctrl+Shift+Esc
- Click on the "New task" button
- Type "msconfig"
- Go to the "Services" tab, and it should be in the list
- Uncheck the box, "Apply" and that's it
However, I don't know what this thing is ... if someone could shed some light on it for me.
It's a program that checks that your software license corresponds to your machine. (anti-piracy software)
Hello,
It seems related to Adobe licensed products, not just Photoshop.
If you have acquired software from the brand, it's probably legitimate.
However, if you installed a printer, software provided with your latest camera or something else, it's more likely to control the use of an optional software related to Adobe, or to encourage you to purchase a license. Business is business...
You can disable it without any problem (and reactivate it if needed in case of a bug with Adobe software). See the steps from arkeen above.
I haven't seen any connection for the moment with products from another brand.
It also seems to be related to a startup process located in the HKCU registry named ISUSPM from Acresso Corp. But be careful before messing with the registry.
If this helps anyone... Happy surfing!
A depressed bit is a bit that has zero morale...
It seems related to Adobe licensed products, not just Photoshop.
If you have acquired software from the brand, it's probably legitimate.
However, if you installed a printer, software provided with your latest camera or something else, it's more likely to control the use of an optional software related to Adobe, or to encourage you to purchase a license. Business is business...
You can disable it without any problem (and reactivate it if needed in case of a bug with Adobe software). See the steps from arkeen above.
I haven't seen any connection for the moment with products from another brand.
It also seems to be related to a startup process located in the HKCU registry named ISUSPM from Acresso Corp. But be careful before messing with the registry.
If this helps anyone... Happy surfing!
A depressed bit is a bit that has zero morale...
Just go to the Start menu: type msconfig
Click on the "Services" tab
And then uncheck > FLEXnet Licensing Service
and confirm the changes ;)
Click on the "Services" tab
And then uncheck > FLEXnet Licensing Service
and confirm the changes ;)
Eéééét no!! It's not enough!! So this thing is a bit like a pox!! First, no uninstaller!! You're not even asked if you agree!! And it installs outside the partitions, there you go for the dark side, the worst!! In sector 32 to be precise, not very far from the MBR (boot program), and for some, go figure, in other sectors in the same area; so there would be several versions, super!! Grub is not happy with it and warns us that we need to inform their authors not to write data in this location (super easy for us users :/) and that it can cause boot problems or others!! (not specified) I can roughly imagine, but that’s a personal opinion regarding everything that’s happening these days. So to eradicate it in addition to your registry keys and your boot manager, it doesn't help to disable the service actually since I didn't even have it myself, but the program was indeed installed as mentioned. Anyway; by searching a bit online, you will find a tutorial from a (British/American) who, unfortunately for the non-initiated, uses Linux to finalize this matter that we are not told about, and of course, these are not the only matters that are being kept from us. The tutorial is therefore on Ubuntu, looking for example Flexnet grub!! from a certain V.......a.
I obviously won't impose Linux in multiboot or anything that would require installing grub, unfortunately, it's up to you to make your choices and understand what needs to be done and/or need to do it. Grub is currently the only detector of this program that alerted me, and it was by looking for a detector of it (under Windows) that I ended up on this thread. Obviously, it’s useless to install grub alone or even dangerous for the booting of your dear OS, but a live CD might potentially do the trick blindly. When I say blindly, I mean that it's possible to follow the steps indicated in the guy's tutorial with a live CD without actually having to install grub because it's him who had alerted me to the presence of this crap. Anyway, none of this is for beginners or those who don't understand these things!!
Good resolutions to all and don't forget, you are responsible for your actions if you mess up... at the same time, we can only blame these "devs" for inventing such crap, especially in such places. Nevertheless, we will die less stupid :) and who knows, maybe we will also become devs one day? since we are being put on this path, what irony.
O'B
I obviously won't impose Linux in multiboot or anything that would require installing grub, unfortunately, it's up to you to make your choices and understand what needs to be done and/or need to do it. Grub is currently the only detector of this program that alerted me, and it was by looking for a detector of it (under Windows) that I ended up on this thread. Obviously, it’s useless to install grub alone or even dangerous for the booting of your dear OS, but a live CD might potentially do the trick blindly. When I say blindly, I mean that it's possible to follow the steps indicated in the guy's tutorial with a live CD without actually having to install grub because it's him who had alerted me to the presence of this crap. Anyway, none of this is for beginners or those who don't understand these things!!
Good resolutions to all and don't forget, you are responsible for your actions if you mess up... at the same time, we can only blame these "devs" for inventing such crap, especially in such places. Nevertheless, we will die less stupid :) and who knows, maybe we will also become devs one day? since we are being put on this path, what irony.
O'B
ah voilà I just discovered this on a very old computer on which I was installing ArchLinux. Be careful, this is very dangerous, do not try this at home, adding zeros in all sectors before the first partition will delete all existing bootloaders (yes, WinDos too).
However, if like me it's on a vintage machine, there are no risks, and you are not afraid to type a few Linux commands ::
all this as root of course and having some knowledge of Linux is better. The first command saves the MBR in /tmp (you need to figure out how to restore it in case of problems); while the second one writes zeros everywhere up to sector 62.
if you were on Linux, grub is removed and needs to be reinstalled, but be careful because you need to re-chroot and completely reinstall it. Here’s how to do it with an ArchLinux live CD, and a 32-bit system (the others are not completely different) ::
However, if like me it's on a vintage machine, there are no risks, and you are not afraid to type a few Linux commands ::
# dd if=/dev/sda of=/tmp/mbr.img bs=512 count=63
# dd if=/dev/zero of=/dev/sda bs=512 count=62 seek=1
all this as root of course and having some knowledge of Linux is better. The first command saves the MBR in /tmp (you need to figure out how to restore it in case of problems); while the second one writes zeros everywhere up to sector 62.
if you were on Linux, grub is removed and needs to be reinstalled, but be careful because you need to re-chroot and completely reinstall it. Here’s how to do it with an ArchLinux live CD, and a 32-bit system (the others are not completely different) ::
# loadkeys fr
# mount /dev/sda1 /mnt
# arch-chroot /mnt /bin/bash
# grub-install --target=i386-pc --recheck /dev/sda
# grub-mkconfig -o /boot/grub/grub.cfg
# umount -R /mnt
# systemctl reboot
Ah there, I just discovered this on a very old computer on which I was installing ArchLinux. Be careful, it's very dangerous, don't try this at home, adding zeros in all sectors before the first partition will delete any existing bootloader (yes, WinDos too).
However, if like me you are on an old rustbucket, there's no risk, and you are not afraid to type a few Linux commands::
all this as root of course, and having some knowledge of Linux is better. The first command backs up the mbr to /tmp (you need to figure out how to restore it in case of problems); while the second puts zeros everywhere up to sector 62.
If you were on Linux, grub is deleted and you need to reinstall it, but be careful because you have to re-chroot and reinstall completely. Here’s how to do it with an ArchLinux live CD and a 32-bit system (others are not completely different)::
However, if like me you are on an old rustbucket, there's no risk, and you are not afraid to type a few Linux commands::
# dd if=/dev/sda of=/tmp/mbr.img bs=512 count=63
# dd if=/dev/zero of=/dev/sda bs=512 count=62 seek=1
all this as root of course, and having some knowledge of Linux is better. The first command backs up the mbr to /tmp (you need to figure out how to restore it in case of problems); while the second puts zeros everywhere up to sector 62.
If you were on Linux, grub is deleted and you need to reinstall it, but be careful because you have to re-chroot and reinstall completely. Here’s how to do it with an ArchLinux live CD and a 32-bit system (others are not completely different)::
# loadkeys fr
# mount /dev/sda1 /mnt
# arch-chroot /mnt /bin/bash
# grub-install --target=i386-pc --recheck /dev/sda
# grub-mkconfig -o /boot/grub/grub.cfg
# umount -R /mnt
# systemctl reboot