Post by Newyana2Post by Jeff BarnettI'm running win 7 SP1 64bit on an otherwise stable computer. My
browser is current Firefox 64 bit and my default pdf reader is Adobe.
Intermittently, I'm receiving the following error message when
"The procedure entry point GetPackageFamilyName could
not be located in the dynamic link library KERNET32.dll."
Note that other than the message, the file seems to be properly loaded
and intermittent means sometimes a particular file will load cleanly
and other times the message is presented. The bad behavior shows up
with more than one file,
I have not noted the problem when clicking on pdf files on my machine,
i.e., they open in in the reader with no problem. It looks like there
was a behind the back Reader update 4/4/2023 but this evening is the
first I've seen of this message. N.B. I have not updated Windows for
about a year.
Anyone have an idea what's going on and how to fix this problem? Any
pointers would be most appreciated.
https://learn.microsoft.com/en-us/windows/win32/api/appmodel/nf-appmodel-getpackagefamilyname
getpackagefamilyname()
Requirements
Minimum supported client Windows 8 [desktop apps only] <===
coding error by Adobe-Bloat-Lard-Department
DLL Kernel32.dll
(conditional usage required, check OSver first)
*******
"Hi,
We have added a UWP app named "Notification Manager for Adobe Reader"
to support push notifications on Win 10 environment. It supports all
types
of notifications about any change in the status of the documents that
you shared for viewing, reviewing and signing. More info is available
at Document Cloud notifications.
Regards,
Rupa Jannela
Acrobat Team
"
*******
"I have just turned it off in Win 10 using the sequence [well, good for
you...]
Settings -> Privacy -> Background Apps -> Notification Manager for
Adobe Acrobat (turn it off)
*******
C:\Program Files (x86)\Adobe\Acrobat DC\Acrobat\
Autoruns isn't much of a solution, because the continuous
reinstallation of software by Adobe ARM, just defeats settings changes.
You might have to use Autoruns once a week, if pursuing the issue this way.
http://live.sysinternals.com/
You need something like an "applocker" that blocks execution of ADNotificationManager.exe .
And since ADNotificationManager.exe is a UWP (like a Metro App), I don't know
if there are any special details or not. Normally the EXE files are not ordinary
EXE files, and they contain a manifest of launch materials. Blocking them might
still interfere with them... a bit.
There is another way ...
To prevent a file being created, create a directory of the same name,
make it read-only, and then remove all permissions from it. Similarly
to prevent a directory being created, create a file of the same name,
make it read-only, and then remove all permissions from it. It's
usually the latter variant I need, to prevent badly-written software
from forcing and using directories in my user profile rather than my
data drive. Of course, the alternative directory or file may well be a
nuisance in its own right, but it may be less than the original nuisance
that you're trying to avoid, and thus worth settling for if no other
form of prevention can be made to work.
Post by Newyana2File bug report with Adobe dumbasses.
Yes.
Post by Newyana2Really, their bloat fleet should have a preference right in the
main viewer, to disable the item. Of course, that's too logical
for high school graduates to follow as a concept.
+1
Post by Newyana2My mouse scroll wheel, does not work in the Preferences panel.
Typical badly-written, badly-tested, bloatware crap.
Adobe also used to, may still, have a Quick Start or similarly-named
program that used to load with Windows, either from the ...
Start Menu\Programs\Startup
... folder, or the ...
HLKM or HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
... registry key. As you say, no matter how often you deleted the
setting from wherever, sooner or later it would just re-install itself.
Its sole purpose was to preload resources that Acrobat Reader needed to
display PDFs, so that, should the user actually want to read a PDF, it
would load quicker than otherwise it would have, but the corollary of
that is that to achieve that marginal saving it slowed Windows
boot/logon time, and if the user never wanted to read a PDF anyway, the
resources loaded were consuming memory and maybe CPU time unnecessarily
for the entire duration of their session. In other words, it was
bloatware, pure and simple.
For myself, I read PDFs with PDF-XChange viewer, and Acrobat Reader has
been uninstalled from all of my systems.
--
Fake news kills!
I may be contacted via the contact address given on my website:
www.macfh.co.uk