inno/windows hangs during C:\Windows\system32\regsvr32.exe” /s "C:\Program Files\PowerArchiver\pashlext64.dll
-
@Brian-Gregory said in inno/windows hangs during C:\Windows\system32\regsvr32.exe” /s "C:\Program Files\PowerArchiver\pashlext64.dll:
This seems to be fixed by renaming the file “C:\Program Files\Box\Box Sync\IconOverlayClient.dll” which is part of BoxSync for Windows available from https://app.box.com/settings/sync
I already thought BoxSync for Windows was utter rubbish compared to DropBox or even GoogleDriveSync but unfortunately I have 50GB free for life on Box and don’t really want to pay for an alternative. But it’s still fairly usable without IconOverlayClient.dll.
thats weird. @mili will test it today on his computer with Box installed and lets see.
-
lets take a look, downloading Box
-
no luck reproducing so far.
Smooth installation while having Box installed and active.attempting on another machine today
-
@Mili Maybe it’s because I also have googledrivesync and dropbox installed.
BTW I’m using Windows 7 (64 bit). -
Thanks! just tried with all 3 and no luck reproducint.
Although, it’s on a W10 64bit machine.
Will try on a W7 64bit machine and give it a go. -
@Brian-Gregory I have recently been trying to find out here whether a sudden rash of Sharpshell errors in my Win7 Event Viewer, which seem to roughly coincide with new releases of PA, are indeed connnected to PA or are caused by something else. The view so far is that there appears to be no possible connection.
Your post raises some interesting possibilities.
Sharpshell.dll is only in the Box Sync subfolder in Program Files on my system, and a number of the errors (which I’ve been trying to pin down via Process Monitor logging) refer to “IconOverlayClient”, “SyncIconOverlay” and so forth, all of which, as you say, are related to dlls in the Box Sync folder.
I’m going to rename Sharpshell.dll and see a) if it stops the errors, b) screws up Box (which I never have running automatically anyway) and c) what other effects it may have system-wide. As it happens, I’m in pretty much the same boat as you vis a vis Box, DropBox and GoogleDrive.
Other than that, my experience is that regsvr32.exe doesn’t go to end and close, and after some reinstallation attempts yesterday I ended up with about 6 instances of it running.
-
@PA_Fan FYI I can make the installation finish by using Task Manager (in all users mode) to kill the offending regsvr32.exe which makes the PA setup pop up an error box which and I can then click on, if I remember correctly, “Ignore” and installation then finishes. I think the PA DLL has even been registered correctly after this, though I’m not 100% certain.
-
@Brian-Gregory Thanks for that info. I’ll try it next time (though I hope it won’t be necessary).
-
@PA_Fan said in inno/windows hangs during C:\Windows\system32\regsvr32.exe” /s "C:\Program Files\PowerArchiver\pashlext64.dll:
@Brian-Gregory I have recently been trying to find out here whether a sudden rash of Sharpshell errors in my Win7 Event Viewer, which seem to roughly coincide with new releases of PA, are indeed connnected to PA or are caused by something else. The view so far is that there appears to be no possible connection.
Your post raises some interesting possibilities.
Sharpshell.dll is only in the Box Sync subfolder in Program Files on my system, and a number of the errors (which I’ve been trying to pin down via Process Monitor logging) refer to “IconOverlayClient”, “SyncIconOverlay” and so forth, all of which, as you say, are related to dlls in the Box Sync folder.
I’m going to rename Sharpshell.dll and see a) if it stops the errors, b) screws up Box (which I never have running automatically anyway) and c) what other effects it may have system-wide. As it happens, I’m in pretty much the same boat as you vis a vis Box, DropBox and GoogleDrive.
Other than that, my experience is that regsvr32.exe doesn’t go to end and close, and after some reinstallation attempts yesterday I ended up with about 6 instances of it running.
as i suggested originally, connection might be that (now we know it is box) box is monitoring folder and setting icon overlays over these icons, or trying to.
It is kind of crazy that they are using some free sdk from internet that has been last updated 3 years ago to build their shell support (based on c#), they likely have several hundred people working there.
-
if we could reproduce this issue here, we could workaround it… so far no go though.
-
@spwolf As you say, it seems pretty sure that Box using Sharpshell is the problem. I see that there is a question about this error on the Box forum, but no-one seems to have tried to answer it in any shape.
I have disabled the .dll, and so far have no errors from Sharpshell. I’m still getting what I think is the associated .NET error, which is infuriating. I cannot see where any Box activity is initiated (Task Scheduler, Startup etc) but I’ll keep looking.
-
@PA_Fan said in inno/windows hangs during C:\Windows\system32\regsvr32.exe” /s "C:\Program Files\PowerArchiver\pashlext64.dll:
@spwolf As you say, it seems pretty sure that Box using Sharpshell is the problem. I see that there is a question about this error on the Box forum, but no-one seems to have tried to answer it in any shape.
I have disabled the .dll, and so far have no errors from Sharpshell. I’m still getting what I think is the associated .NET error, which is infuriating. I cannot see where any Box activity is initiated (Task Scheduler, Startup etc) but I’ll keep looking.
people are likely not checking their error logs :).
I just installed it on my main desktop, and i see that icon in taskbar is not set properly, so Win10 is showing their “empty” image there…
-
@PA_Fan I suspect Box has also done regsvr32.exe on some of it’s DLLs so that things going on elsewhere (I suspect mainly in explorer.exe) can cause activity in box’s DLLs.
-
i was just checking temp folder for pa debugs, and i see that box put overlay icons there… they are broken icons though, maybe thats why there is a problem. They show as unknown image in windows explorer but when you click on it, it is sync/notsync icons.
-
@Brian-Gregory I see there are a host of logfiles for Box in my folder C:\Users\XXXX\AppData\Local\Box Sync\Logs, with entries like this:-
“2017-01-26 10:15:20,049 [1] INFO - IconOverlayClient.ProblemIconOverlay: BoxSyncProblem setting up its icon
2017-01-26 10:15:20,065 [1] INFO - IconOverlayClient.SyncedIconOverlay: BoxSyncSynced setting up its icon”Even if the PA problems aren’t fully identified, it now seems to me that my Sharpshell problems are unquestionably down to Box. They also seem to date to the first of these logfiles. It’s still a bit of mystery as to what’s been happening with Box.
-
@Brian-Gregory I managed to see some of what’s happening via Process Explorer. The Box DLLs are tied into Explorer, and the Free Commander (Explorer-type and based utility) context/shell FCcontextMenu64. There’s also a tie into Firefox, which I guess must also be somehow Explorer-related.
-
@PA_Fan i would guess thats everywhere where you right clicked and got shell menu.
You can disable their dll from loading by using shellexview
-
I’m abandoning BoxSync. I’m fed up with it. It just decided it didn’t like me prodding and poking at it trying to get it to behave itself and needs to re-upload a big chunk of my stuff, which it says will take 17 hours. I know this isn’t true though. It’ll take ages and ages and will require me to restart it many times because it times out and says many files have failed to sync. It’d help if it didn’t try and upload dozens of files all at the same time but Box insist that’s how it’s supposed to be and if I don’t like it more or less making my internet connection unusable for any other purpose while it uploads then it’s just tough. I will pay for 100GB in Google Drive.
-
we had @JRSPowerArchiver report something similar during installation. I would guess it is also due to box install then?
I have also moved thread from alpha forums to main forums so other users can see it.
-
@spwolf I’m pretty sure that it is down to Box, as everything began working OK after I carried out the .dll renaming and other actions discussed above.
Sharpshell errors no longer appeared in the Event Viewer, either.
I’m still not exactly sure which elements of PA, Box and Explorer were causing this, why and how, but it’s no longer a problem for me (not that I use Box much anyway), and I think @Brian-Gregory has stopped using it altogether.
