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. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
Quicksilver Lite Won't Load
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. |
#2
|
|||
|
|||
Quicksilver Lite Won't Load
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. The name Program Files was a Microsoft brainfart. The space between the two words has caused decades of software problems. 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. |
#3
|
|||
|
|||
Quicksilver Lite Won't Load
In article ci.org Anonymous 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. The name Program Files was a Microsoft brainfart. The space between the two words has caused decades of software problems. Learn to read. That single meaningless space between two words has less to do with it than the empty space between your ears. The Program Files folders now have permissions that prevent applications and dumb users from changing file and folder contents. You don't run programs that will be changing files or creating new ones in that location. It's a security risk. 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. |
#4
|
|||
|
|||
Quicksilver Lite Won't Load
That single meaningless space between two words has less to do with it than the empty space between your ears. I am always glad to see people like you show themselves to be the compete son of a bitch they truly are. |
#5
|
|||
|
|||
Quicksilver Lite Won't Load
In article
Anonymous wrote: That single meaningless space between two words has less to do with it than the empty space between your ears. I am always glad to see people like you show themselves to be the compete son of a bitch they truly are. Lol! |
#6
|
|||
|
|||
Quicksilver Lite Won't Load
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. |
#7
|
|||
|
|||
Quicksilver Lite Won't Load
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 |
#8
|
|||
|
|||
Quicksilver Lite Won't Load
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. |
#9
|
|||
|
|||
Quicksilver Lite Won't Load
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. Short answer (my other post isn't coming through)... Go to "qsl.exe", right-click, do Properties, use the Compatibility tab, set the OS in there to Vista SP2. I'm sure some other values in that OS choice selector will work too, and that value was just the first one I tested. That's a workaround. It really shouldn't work on a 0xC0000005 access violation, but it did work and I'm not complaining. Paul |
#10
|
|||
|
|||
Quicksilver Lite Won't Load
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 |
#11
|
|||
|
|||
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. |
#12
|
|||
|
|||
Quicksilver Lite Won't Load
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. |
#13
|
|||
|
|||
Quicksilver Lite Won't Load
On 11/7/2017 8:58 PM, 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. Yeah, this coming from someone who's living in mommy's basement. |
#14
|
|||
|
|||
Quicksilver Lite Won't Load
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. Another anonymous son of a bitch answers. |
#15
|
|||
|
|||
Quicksilver Lite Won't Load
In article emailer.net
Fritz Wuehler wrote: Another anonymous son of a bitch answers. PKB |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|