inno/windows hangs during C:\Windows\system32\regsvr32.exe” /s "C:\Program Files\PowerArchiver\pashlext64.dll
-
@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.
-
@PA_Fan said in inno/windows hangs during C:\Windows\system32\regsvr32.exe” /s "C:\Program Files\PowerArchiver\pashlext64.dll:
@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.
yeah, i am aware… but there are many other users who cant quite box even if windows version really does seem to be a shoddy piece of software, regardless of PA issue or not.
So next week we will be working around this problem to see if it is fixable from our end.
Thanks!
-
Hello guys, please check this release to see if there are any changes to this problem:
https://forums.powerarchiver.com/topic/5738/fast-ring-powerarchiver-2017-17-00-64 -
Experiencing the same thing when trying to deploy PA 2017 with SCCM.
If i run the cmd file locally on the computer it runs the installation smoothly, but when io try to deploy it the deployment crashes.
I have about 600computers that i need to deploy this program to so it would be nice if you could try to fix it. -
@Carlos-Martin-Moreno said in inno/windows hangs during C:\Windows\system32\regsvr32.exe” /s "C:\Program Files\PowerArchiver\pashlext64.dll:
Experiencing the same thing when trying to deploy PA 2017 with SCCM.
If i run the cmd file locally on the computer it runs the installation smoothly, but when io try to deploy it the deployment crashes.
I have about 600computers that i need to deploy this program to so it would be nice if you could try to fix it.Hi Carlos,
Please try with 65:
http://dl.powerarchiver.com/2017/powarc170065.exeLet us know if that works OK
Thanks!
-
@Carlos-Martin-Moreno said in inno/windows hangs during C:\Windows\system32\regsvr32.exe” /s "C:\Program Files\PowerArchiver\pashlext64.dll:
Experiencing the same thing when trying to deploy PA 2017 with SCCM.
If i run the cmd file locally on the computer it runs the installation smoothly, but when io try to deploy it the deployment crashes.
I have about 600computers that i need to deploy this program to so it would be nice if you could try to fix it.keep in mind that PA 2017 is Beta 1 still… by final (in May?) there will also be MSI installation that will be easier to use for business/enterprise installations.





