A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Windows 10 » Windows 10 Help Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Quicksilver Lite Won't Load



 
 
Thread Tools Rate Thread Display Modes
  #16  
Old November 9th 17, 08:18 PM posted to alt.privacy.anon-server,alt.comp.os.windows-10
Jack[_24_]
external usenet poster
 
Posts: 8
Default Quicksilver Lite Won't Load

On 11/8/2017 9:06 PM, Paul wrote:
Jack wrote:
On 11/7/2017 8:45 PM, Paul wrote:
Jack wrote:
On 11/7/2017 3:16 AM, Anonymous Remailer (austria) wrote:
In article
Jack wrote:
After an update to Windows 10 this morning, I get this error message
when I try to launch QSA:
I call bull****.Â* Unless you just reinstalled or turned the computer
on after being off a month, there won't be any Windows 10
updates/downloads until Tuesday of next week.

I failed to load mixlib.dll in my home directory! The error reported
was: A dynamic link library (DLL) initialization routine failed.
Remove it and install it somewhere besides a "Program Files"
directory.

Is there a way to extract mixlib.dll from the install process for
QSA or
do I have to do a new installation to resolve this issue.
New.

You can call it anything you want. I'm reporting what happened to me
PERIOD. I also did NOT previously install QSL in Program Files
directory. I will try to do a re-installation and see what happens.
Version of QSL (URL if you like) ?

Version of Windows (run "winver" from right-click Run box) ?
32 or 64 bit ? (See System control panel for a hint.)

Windows Defender as your AV ?
Third-party AV (which disabled Windows Defender) ?
Heuristic detection enabled ?

Have you just enabled Controlled Folder Access, with
Windows Defender as your AV ? That's a brand new feature,
which comes... turned off. You might see that offered on
16299.xx, as of just a few days ago (Oct.26 or so?).
I see articles similar to this one, around that date.

https://www.ghacks.net/2017/10/24/co...in-windows-10/



A scan of QSL on virustotal.com shows a couple false
positives for the DLLs, from some of the lesser-known
AV products, which is "noise" in the whole picture, and
will not cause a problem.

The DLLs are not signed. They're not likely to be
regsvr32-able, and the program itself is probably
loading the libraries as some sort of dylib. Again,
not expected to be a problem, but I'm not a software
developer...

Note that some of the more scummy AV products, have a
"reputation" based analysis, where they call something
"malware" if nobody is downloading it. If the signature
of the executable isn't in their database, the idea is
that nobody is using it and it's not to be trusted.
It's not a very clever or valuable technique, but it
is a cheap thing for these companies to administer. And
I know this ****es off some of the small developers who
write utilities for us (because they're the ones getting
slapped around by it).

If you want to "watch what happens", you can run ProcMon
before trying to launch the program, then disable
trace collection by unticking the box in the file menu.
That stops the trace and you can scroll through the events
at your leisure. By setting certain filters, such as
"program name" "is" "qsl.exe", you can adjust the trace
so more relevant results are presented. (The filter only
affects what is visible, not what is captured.) Selecting
"clear" from the Edit menu, prepares for your next trace.
Ticking the box again in the File menu, starts the next
trace running. You should begin the trace, before launching
the troublesome program.

https://docs.microsoft.com/en-us/sys...nloads/procmon

The 64-bit trace is not readable on a 32-bit machine, so there
can be limits in terms of transferring the trace to another
machine for analysis. It's not WinDBG by any stretch of the
imagination, but it is accessible. It produces a lot of output.
Only occasionally, does it give you the hint you need. For
example, I had to go through around 100,000 lines of output
once, to find a missing registry key. And got my sound
working again :-) That was pure luck, not skill.

Procmon is mainly for being able to say "at least
I tried to figure it out".

Â*Â* Paul


After some further testing I just noticed that I got an
"EAccessViolation" error message when trying to load QSL. Please note I
reinstalled QSL to its own directory off of the C: drive. This is a
64bit computer running Windows 10.


OK, figured it out.

Go to your QSL folder. No, it doesn't have to be
in Program Files. It can be other places if you want.

Right-click "qsl.exe" and do Properties. There is a Compatibility
tab in the dialog. Look down a bit, and you "get to pick your OS".
The loader has the ability to "emulate" earlier OSes, to make
older programs "comfortable".

Even though you're on Windows 10, you can set the Compatibility
to "Vista SP2" as an example. Close the Properties when you're done.

Now, start "qsl.exe" and it should get past the problem with mixlib.dll.

*******

1) I tried Procmon. I could see it bombing, but there was no actual line
where
Â*Â* the LoadLibrary actually executes. In fact, I suspect it actually
loaded,
Â*Â* but the address returned might have been munged or something (maybe
ASLR?).

2) I noticed, as a marker, that Windows "werfault.exe" was running. That's
Â*Â* where, instead of making a nice log for the user to read, the OS zips
Â*Â* up the details and sends them off to Microsoft. I did actually find...

Â*Â*
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\A ppCrash_qsl.exe_f6a0f3263f529edefd75ec5493626dda77 e1710_d51bd0e6_0ae51b45\report.wer


Â*Â* which is a text file. However, the problem is 0xC0000005 in there,
Â*Â* which from memory is an Access Violation. That's why I'm guessing the
Â*Â* LoadLibrary succeeded, a non-zero result was returned, qsl.exe
Â*Â* tried to index that location, and the number wasn't actually
Â*Â* ready to be used as a DLL handle. Perhaps the LoadLibrary handler
Â*Â* needs to be re-written for a "hardened" OS.

3) One thing I tried, was disabling NX (No execute) entirely

Â*Â*Â*Â*Â* bcdedit.exe /set {current} nx AlwaysOff

Â*Â* then later

Â*Â*Â*Â*Â* bcdedit.exe /set {current} nx OptIn

Â*Â* but discouragingly, that didn't help.

4) Then, just out of the blue, I decided to try
Â*Â* to punt on third down, and use the Compatibility interface,
Â*Â* and (try) to fix it that way. There's really no reason
Â*Â* for that to work on a C0000005, but I'd run out of bullets.

And to answer your question, I haven't a clue why "suddenly"
the Compatibility thing is needed. But, it's a workaround
for now.

Â*Â* Paul


Paul thanks for the suggestions above. I elected to delete my qsl folder
and start from scratch. However, I saved my qsl.ini file and my qs.db
file and copied these over the re-installed files. My problem went away.
I will store your suggestions above for future reference.
Ads
  #17  
Old November 10th 17, 07:51 AM posted to alt.privacy.anon-server,alt.comp.os.windows-10
Anonymous
external usenet poster
 
Posts: 403
Default Quicksilver Lite Won't Load

In article k
Nathan Hale wrote:

In article
Jack wrote:

On 11/7/2017 3:16 AM, Anonymous Remailer (austria) wrote:

In article
Jack wrote:

After an update to Windows 10 this morning, I get this error message
when I try to launch QSA:

I call bull****. Unless you just reinstalled or turned the
computer on after being off a month, there won't be any Windows
10 updates/downloads until Tuesday of next week.

I failed to load mixlib.dll in my home directory! The error reported
was: A dynamic link library (DLL) initialization routine failed.

Remove it and install it somewhere besides a "Program Files"
directory.

Is there a way to extract mixlib.dll from the install process for QSA or
do I have to do a new installation to resolve this issue.

New.

You can call it anything you want. I'm reporting what happened to me
PERIOD. I also did NOT previously install QSL in Program Files
directory. I will try to do a re-installation and see what happens.


maybe windows 10 is too complicated for you. should run vista
instead.*


Asshole

 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 09:45 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.