Log in

View Full Version : SMSC Uninstall


steky9
03-29-2017, 03:17 PM
I'm trying to install the DisplayLink drivers, but it fails as it detects the SMSC drivers which were previously installed. I've uninstalled SMSC as much as possible, even going to using Revo Uninstaller to remove any trace of it, and still no use.

I've tried the compatibility check tool as well, and it doesn't create a log file in "C:\Program Files\DisplayLink Core Software\Debug\". In fact it doesn't even create the "C:\Program Files\DisplayLink Core Software\" directory, however it does create a DiCompatCheck.log file in the same directory I run the compatibility tool from. I've tried to attach it, but its regarded as an invalid file

rboerner
03-29-2017, 03:20 PM
If you follow the steps here does that help? http://support.displaylink.com/knowledgebase/articles/544327

steky9
03-29-2017, 04:09 PM
Yes did all that. I uninstalled the ViewSpan software first and then SMSC Core Software (although it required Revo to do it fully). I've also checked and the folder SGFX folder no longer exists in C:\Program Files. Then tried deleting the services manually via CMD but they were already removed.

ie


C:\windows\system32>sc delete SGFXMgr
[SC] OpenService FAILED 1060:

The specified service does not exist as an installed service.


C:\windows\system32>

steky9
03-29-2017, 04:46 PM
In case it helps I've posted the DiCompatCheck.log output to Pastebin

https://pastebin.com/dUyHiycE

Tried a few things, that didn't work, but the DlCompatCheck.log contents change, so putting up a new link just in case there's a difference when its decoded

https://pastebin.com/U8nGNf2Y

AlbanRampon
03-30-2017, 03:37 PM
Hello,

The service installed is SGFX

Would you please try use:
sc delete SGFX

Kind regards,
Alban

steky9
03-30-2017, 04:25 PM
No luck


C:\windows\system32>sc delete SGFX
[SC] OpenService FAILED 1060:

The specified service does not exist as an installed service.


C:\windows\system32>


I can do a "sc query >> c:\temp\service.txt" and then search through it for any mention of SGFX or SMSC or similar, but nothing shows up.

Is it searching through the registry for SGFX?.

steky9
03-30-2017, 07:50 PM
Using the support tool, and searching for SGFX, I find the following section in setupapi.dev.log


>>> [Import Driver Package - c:\users\ekelste\appdata\local\temp\{5b62e0c3-2b90-4367-983c-206273e4502a}\viewspan_x64\smscufx.inf]
>>> Section start 2017/03/29 08:23:06.868
cmd: C:\Users\ekelste\AppData\Local\Temp\{5B62E0C3-2B90-4367-983C-206273E4502A}\viewspan_x64\dpinst.exe /SA /SW /SE
sto: Importing driver package into Driver Store:
sto: Driver Store = C:\windows\System32\DriverStore (Online | 6.1.7601)
sto: Driver Package = c:\users\ekelste\appdata\local\temp\{5b62e0c3-2b90-4367-983c-206273e4502a}\viewspan_x64\smscufx.inf
sto: Architecture = amd64
sto: Locale Name = neutral
sto: Flags = 0x00000000
sto: Copying driver package files to 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}'.
inf: Opened INF: 'c:\users\ekelste\appdata\local\temp\{5b62e0c3-2b90-4367-983c-206273e4502a}\viewspan_x64\smscufx.inf' ([strings])
inf: Opened INF: 'C:\windows\System32\DriverStore\FileRepository\wi nusb.inf_amd64_neutral_6cb50ae9f480775b\winusb.inf ' ([strings.0409])
inf: Opened INF: 'c:\users\ekelste\appdata\local\temp\{5b62e0c3-2b90-4367-983c-206273e4502a}\viewspan_x64\smscufx.inf' ([strings])
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000000
flq: SourceRootPath - 'c:\users\ekelste\appdata\local\temp\{5b62e0c3-2b90-4367-983c-206273e4502a}\viewspan_x64'
flq: SourceFilename - 'WdfCoInstaller01011.dll'
flq: TargetDirectory- 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000000
flq: SourceRootPath - 'c:\users\ekelste\appdata\local\temp\{5b62e0c3-2b90-4367-983c-206273e4502a}\viewspan_x64'
flq: SourceFilename - 'WdfCoInstaller01009.dll'
flq: TargetDirectory- 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000000
flq: SourceRootPath - 'c:\users\ekelste\appdata\local\temp\{5b62e0c3-2b90-4367-983c-206273e4502a}\viewspan_x64'
flq: SourceFilename - 'smscufx.cat'
flq: TargetDirectory- 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000000
flq: SourceRootPath - 'c:\users\ekelste\appdata\local\temp\{5b62e0c3-2b90-4367-983c-206273e4502a}\viewspan_x64'
flq: SourceFilename - 'smscufx.inf'
flq: TargetDirectory- 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000000
flq: SourceRootPath - 'c:\users\ekelste\appdata\local\temp\{5b62e0c3-2b90-4367-983c-206273e4502a}\viewspan_x64'
flq: SourceFilename - 'winusbcoinstaller2.dll'
flq: TargetDirectory- 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000000
flq: SourceRootPath - 'c:\users\ekelste\appdata\local\temp\{5b62e0c3-2b90-4367-983c-206273e4502a}\viewspan_x64'
flq: SourceFilename - 'SgfxSetup.exe'
flq: TargetDirectory- 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {FILE_QUEUE_COPY}
flq: CopyStyle - 0x00000000
flq: SourceRootPath - 'c:\users\ekelste\appdata\local\temp\{5b62e0c3-2b90-4367-983c-206273e4502a}\viewspan_x64'
flq: SourceFilename - 'SgfxCoInstaller1.dll'
flq: TargetDirectory- 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}'
flq: {FILE_QUEUE_COPY exit(0x00000000)}
flq: {_commit_file_queue}
flq: CommitQ DelNodes=0 RenNodes=0 CopyNodes=7
flq: {_commit_copy_subqueue}
flq: subqueue count=7
flq: source media:
flq: SourcePath - [c:\users\ekelste\appdata\local\temp\{5b62e0c3-2b90-4367-983c-206273e4502a}\viewspan_x64]
flq: SourceFile - [WdfCoInstaller01011.dll]
flq: Flags - 0x00000000
flq: {_commit_copyfile}
flq: CopyFile: 'c:\users\ekelste\appdata\local\temp\{5b62e0c3-2b90-4367-983c-206273e4502a}\viewspan_x64\WdfCoInstaller01011.dll '
flq: to: 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}\SET2E0A.tmp'
flq: MoveFile: 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}\SET2E0A.tmp'
flq: to: 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}\WdfCoInstaller01011.dll'
flq: {_commit_copyfile exit OK}
flq: {_commit_copyfile}
flq: CopyFile: 'c:\users\ekelste\appdata\local\temp\{5b62e0c3-2b90-4367-983c-206273e4502a}\viewspan_x64\WdfCoInstaller01009.dll '
flq: to: 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}\SET2E1B.tmp'
flq: MoveFile: 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}\SET2E1B.tmp'
flq: to: 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}\WdfCoInstaller01009.dll'
flq: {_commit_copyfile exit OK}
flq: {_commit_copyfile}
flq: CopyFile: 'c:\users\ekelste\appdata\local\temp\{5b62e0c3-2b90-4367-983c-206273e4502a}\viewspan_x64\smscufx.cat'
flq: to: 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}\SET2E2B.tmp'
flq: MoveFile: 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}\SET2E2B.tmp'
flq: to: 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}\smscufx.cat'
flq: {_commit_copyfile exit OK}
flq: {_commit_copyfile}
flq: CopyFile: 'c:\users\ekelste\appdata\local\temp\{5b62e0c3-2b90-4367-983c-206273e4502a}\viewspan_x64\smscufx.inf'
flq: to: 'C:\Users\ekelste\AppData\Local\Temp\{38d7f144-3aae-41cb-3df1-836f3ac66629}\SET2E2C.tmp'


but none of these files exists in the directories shown. Instead they seem to exist in "C:\Windows\System32\DriverStore\FileRepository\sms cufx.inf_amd64_neutral_f621a53b75ad332d", but I cannot delete them from there as it requires System privileges


C:\Windows\System32\DriverStore\FileRepository\sms cufx.inf_amd64_neutral_f621a53
b75ad332d>dir
Volume in drive C is OSDISK
Volume Serial Number is 067C-528A

Directory of C:\Windows\System32\DriverStore\FileRepository\sms cufx.inf_amd64_n
eutral_f621a53b75ad332d

03/29/2017 08:23 AM <DIR> .
03/29/2017 08:23 AM <DIR> ..
05/02/2013 05:24 AM 40,184 SgfxCoInstaller1.dll
05/02/2013 05:28 AM 11,455,600 SgfxSetup.exe
05/03/2013 02:17 PM 12,677 smscufx.cat
05/02/2013 05:28 AM 11,000 smscufx.inf
03/29/2017 08:23 AM 32,900 smscufx.PNF
05/02/2013 05:28 AM 1,721,576 WdfCoInstaller01009.dll
05/02/2013 05:28 AM 1,795,952 WdfCoInstaller01011.dll
05/02/2013 05:28 AM 1,002,728 winusbcoinstaller2.dll
8 File(s) 16,072,617 bytes
2 Dir(s) 86,527,201,280 bytes free

C:\Windows\System32\DriverStore\FileRepository\sms cufx.inf_amd64_neutral_f621a53
b75ad332d>del *.*
C:\Windows\System32\DriverStore\FileRepository\sms cufx.inf_amd64_neutral_f621a53
b75ad332d\*.*, Are you sure (Y/N)? y
C:\Windows\System32\DriverStore\FileRepository\sms cufx.inf_amd64_neutral_f621a53
b75ad332d\SgfxCoInstaller1.dll
Access is denied.
C:\Windows\System32\DriverStore\FileRepository\sms cufx.inf_amd64_neutral_f621a53
b75ad332d\SgfxSetup.exe
Access is denied.
C:\Windows\System32\DriverStore\FileRepository\sms cufx.inf_amd64_neutral_f621a53
b75ad332d\smscufx.cat
Access is denied.
C:\Windows\System32\DriverStore\FileRepository\sms cufx.inf_amd64_neutral_f621a53
b75ad332d\smscufx.inf
Access is denied.
C:\Windows\System32\DriverStore\FileRepository\sms cufx.inf_amd64_neutral_f621a53
b75ad332d\smscufx.PNF
Access is denied.
C:\Windows\System32\DriverStore\FileRepository\sms cufx.inf_amd64_neutral_f621a53
b75ad332d\WdfCoInstaller01009.dll
Access is denied.
C:\Windows\System32\DriverStore\FileRepository\sms cufx.inf_amd64_neutral_f621a53
b75ad332d\WdfCoInstaller01011.dll
Access is denied.
C:\Windows\System32\DriverStore\FileRepository\sms cufx.inf_amd64_neutral_f621a53
b75ad332d\winusbcoinstaller2.dll
Access is denied.

C:\Windows\System32\DriverStore\FileRepository\sms cufx.inf_amd64_neutral_f621a53
b75ad332d>


Is there an option other than wiping and re-installing?

steky9
03-30-2017, 10:21 PM
Got those files deleted now, and re-ran the support tool, but it still gives the same output. I'm thinking then that it has to be pulling this information from either a log file or else the registry?

AlbanRampon
03-31-2017, 08:24 AM
Hello,

I'm sorry, I replied whilst on mobile and did not read logs properly.

HKEY_LOCAL_MACHINE\SOFTWARE\SGFX is detected. This is not a service, but the folder for the software itself, therefore you cannot remove it with "sc delete".
Do you need the command line or are you comfortable enough going in regedit to remove that?

Kind regards,
Alban

steky9
03-31-2017, 09:03 PM
Don't see that folder there. You sure its the right one?

http://imgur.com/a/punkZ

steky9
03-31-2017, 09:09 PM
BTW Latest output.. I've been trying multiple things to get it to work, so maybe the cause has changed since

https://pastebin.com/Ccyp99wz

AlbanRampon
03-31-2017, 09:16 PM
So now, there is
Found installed software for upgrade code: {70F436D8-E3ED-4304-8B43-09448591E9E5}.
I'd advise scanning the registry for that one.

steky9
04-01-2017, 04:23 PM
No luck, not even for a subset of it like 09448591E9E5 or {70F436D8

AlbanRampon
04-01-2017, 06:23 PM
Hello,
That's annoying. I really wish their uninstaller was a bit more tidy...
For upgrade codes, we don't troll the registry, I've just looked in the code: we only ask Windows if that product is installed or not. And here Windows says yes.

This upgrade code matches SMSC UFX7000 / UFX6000 Software - Release 5.3.60.6579 (http://ww1.microchip.com/downloads/en//softwarelibrary/obj-ufxx000-windows/sgfxsetup-5_3_60_6579.txt)

Could you check what's in the add/remove software along those lines?
If not, can you try to install and then remove it?
http://www.cablematters.com/download/USB3_to_HDMI/SgfxSetup-5_3_60_6579.exe

Kind regards,
Alban

steky9
04-02-2017, 03:42 AM
Hmmm got this to work by re-installing and then uninstalling again. I'd done this days ago too and it didn't work then, so not quite sure why it worked now.

Removed the laptop from the docking station, rebooted, did the complete uninstall via Revo, rebooted again, and then re-attempted to install the DisplayLink driver and it worked.

None of that should have made a difference from before but it did.

AlbanRampon
04-03-2017, 02:40 PM
Glad we finally removed that sticky driver...!