Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER Bug Reports

Reply
 
Thread Tools Display Modes
Old 10-13-2016, 07:25 PM   #1
DenverDavefromDetroit
Human being with feelings
 
Join Date: Oct 2016
Posts: 3
Default [5.25+] First Run VST Scan Error on a Surafce Pro 4

Windows 10
Version 1607
OS 14393.
i7-6650U
16GB

Reaper.exe - bad image

On first run, starting for me with version 5+, VST scan reveals errors in scanning .DLLs from the system directory. One such error attached. Continues ad nauseam until application ultimately fails.

Thanks.
Attached Images
File Type: png reaper error.PNG (29.8 KB, 408 views)
Attached Files
File Type: txt reaper eventvwr.txt (685 Bytes, 318 views)

Last edited by DenverDavefromDetroit; 10-14-2016 at 03:17 PM.
DenverDavefromDetroit is offline   Reply With Quote
Old 10-13-2016, 07:31 PM   #2
foxAsteria
Human being with feelings
 
foxAsteria's Avatar
 
Join Date: Dec 2009
Location: Oblivion
Posts: 10,255
Default

Don't believe that has anything to do with Reaper. Google "Winsxs error" to sort it out.

But are you sure you've added the correct folders to scan for vst's in Reaper prefs? Many non-VST .dll files are found all over your hard disk and will crash Reaper when it tries to load them as plugins. Reaper should only be scanning folders you actually have installed your plugins. Looks like you have Reaper scanning your entire C: drive for plugins.

Welcome to the forums, btw.
__________________
foxyyymusic
foxAsteria is offline   Reply With Quote
Old 10-14-2016, 01:11 AM   #3
ivansc
Human being with feelings
 
Join Date: Aug 2007
Location: Near Cambridge UK and Near Questembert, France
Posts: 22,754
Default

Not sure if I understand you correctly, but IF as you say Reaper is scanning the system directory, that is your problem. There are a zillion non-"VST plugin" .dll files in that directory, none of which are going to be compatible with Reaper. Hence the error reporting.
Once you point reaper at the directory where your actual plugin .dlls reside, I suspect all will be well, but in any case welcone to the forums!


OOPS! Fox beat me to it
__________________
Ici on parles Franglais
ivansc is offline   Reply With Quote
Old 10-14-2016, 03:22 PM   #4
DenverDavefromDetroit
Human being with feelings
 
Join Date: Oct 2016
Posts: 3
Default

Thanks for the welcome. This happens on first run after install, so I can check .configs if that's possible to do and correct them, but I can't run the application to change via GUI. Can't even launch Reaper. Going to go over the installation process and capture some more logs.
DenverDavefromDetroit is offline   Reply With Quote
Old 10-14-2016, 08:39 PM   #5
foxAsteria
Human being with feelings
 
foxAsteria's Avatar
 
Join Date: Dec 2009
Location: Oblivion
Posts: 10,255
Default

This is not default behavior. Have you tried re-installation? If so, just search for a file called Reaper.ini and delete it. Reaper should default back to default VST paths. Or if there is an entry in your start menu for Reaper (reset to factory default) you can run that instead. I'm not familiar with the OS on surface pro. Is it made to run normal applications?
__________________
foxyyymusic
foxAsteria is offline   Reply With Quote
Old 10-14-2016, 10:14 PM   #6
DenverDavefromDetroit
Human being with feelings
 
Join Date: Oct 2016
Posts: 3
Default Reaper .ini persistence?

Thanks all. Powered thru VST scan and, sure enough, C: was in the preferences. Must have made its way in there from user error from a previous install?
DenverDavefromDetroit is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 01:19 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.