First off, it definitely sounds like Scrivener isn’t using the Microsoft Office converters at all. These should be available for DOC, DOCX and PDF if you have MS Office 2007-2013 installed, so if you’ve dealt with the BitDefender issue, try setting them up in Scrivener. In Tools > Options, click the Import/Export tab, then click “Export Converters…” and choose the DOC format from the left drop-down menu and “Microsoft Office” from the right. Repeat for DOCX and PDF, then click OK a couple times to close out of options and try compiling to one of those formats. Does that work for you?
If the Office converters aren’t working, I’d try setting DOC to “RTF-based” instead of Doc2Any, which I’m guessing is what it’s using now. The D2A converter doesn’t support a lot of features, such as the page breaks, so it’s really only the best option when you don’t have MS Office available and your word processor won’t read RTF files, such as happens with a few iOS and Android apps. In that case you may want to compile to DOC using the Doc2Any converter so you can do some editing on your mobile device and then copy the changes to Scrivener later. For you, the RTF-based option will be much better; Word will open it without issue, and it will retain all the features that a regular RTF compile does.
For DOCX, if the Microsoft converters aren’t available, “Scrivener” is the only option, and for heavily formatted files especially that can sometimes produce the “corrupted” message when opening in Word. Usually you can click through it enough to have Word open the file anyway (maybe “repairing” it as part of the process)–it’s not generally an issue with the any of the text in the file, but that some flag in the file format written by the converter isn’t rendered a way Word expects. Once you have it open in Word, you can re-save it, so you should avoid any of the “corrupted” messages in future. That said, there’s really no reason not to just compile to RTF or the RTF-based DOC file and then resave it in Word to the DOCX format, since RTF will be less lossy. (It may not matter, of course, but for instance if you’ve used Scrivener links in your project, they’ll compile as internal links using RTF but are not supported using the “Scrivener” converter for DOCX and will be removed.)
I can’t really say what’s going on with the PDF file that it’s creating an image rather than text; that isn’t something I’ve seen before with either converter. I’d try the Microsoft Office converter for PDF if it’s an option, and otherwise you may be best compiling to RTF and then saving to PDF from Word. If it’s possible to share a sample project that demonstrates this issue when compiled to PDF, though, I’d like to take a look.
As far as the indent, that seems more like a formatting issue somewhere in the project rather than a converter problem. If you are overriding the formatting during compile, take a look at the Formatting section there to see how the indents are set for main text in the row for the document type and level that first chapter is (especially likely if it is different from the other chapters). If you’re not overriding formatting, check the file directly in the editor and make sure the indents are as expected (you can toggle the ruler from the Format menu). It could be you’ve set “Compile as-is” for that first chapter and so it’s compiling differently from the others.