![]() ![]() ![]() I notice that WinPE seems to be missing some OLE-related functions at stock compared to WinRE (Multicommander etc wouldn't run either because oledlg.dll was missing). ![]() Things you can try:ġ) Look at process monitor for file dependency issues. Nvm I see that you did this.Ģ) If nothing obvious sticks out, run the following from command prompt to rule out DLL registration issues (sometimes they don't get carried over with the syswow64 regkeys, I am not sure why):įor /f "delims=*" %a in (x:\wow64.txt) do (x:\windows\syswow64\regsvr32.exe /s x:\windows\syswow64\%a)ģ) If that still doesn't fix it, launch RegShot and take a shot before and after opening excel, then compare. I think I originally had the same error as you. Great to hear! As for XYplorer, all I had to do was regsvr32 syswow64\oleaut32.dll. Spleen, what exactly did you do to fix your XYPlorer issue? I ran Procmon on it and compared "before and after Excel", but couldn't find anything. Maybe it does some initializing somewhere, but I can't tell what or where. The odd thing is: if I run my old portable Excel '97 first and then try XYPlorer again, it runs fine! Running this old Excel in PE is just a "joke", actually, and I found out by accident it fixes the XYPlorer issue, but running it must do "something" to fix the issue. Next issue for me is a bit of a strange one: If I run XYPlorer (which is 32bit only), I get an error ("-2147319780"), which I never have on a normal PESE. Success!! I made a new basic Win10PESE build (enUS this time), used enUS PE and enUS PESE, ran my new script on it (takes 2 minutes) and things are working just fine. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |