Untested windows version detected

‘Untested Windows version 10.0 detected’ error when launching Amazon Kindle for PC

I get this error when launching Amazon Kindle for PC. The notification shows up for half a second, then disappears and nothing happens. It doesn’t show in the task manager either.

Any fixes? Help is appreciated

Replies (7) 

Does Kindle show and does it work?

This is the Windows 10 Insider Preview forum. We are testing preview builds not yet released to the public.

The forum for the public release of Windows 10 is below.

Windows 10 help is found here;

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

That was just my fault. I had just used that with another that was in the other forum and should not have.

Basically this is what I meant;

To help us to help you and to properly get answers to your post you should include some minimum information.

1. Device type. ie Desktop, Laptop, Tablet, Surface, Phone

2. Who made it and model, HDD size. If home built what type motherboard, Intel, AMD

3. OS type, Home, Pro, Enterprise, etc

4. Current build. Hit the WIN key, type winver, hit Enter.

My Kindle is working and just updated on my public release Desktop.

Qt: Untested Windows version 6.2 detected! #64

Comments

AvinashTompe commented Sep 18, 2014

its working on my local system but after hosting on server getting following error
i am using windows server-2012 and iis 8.0

Qt: Could not initialize OLE (error 80070005)
Error: Failed loading page http://xxxxxxx.com/CompanyUsers/Invoices/viewPdf/393 (sometimes it will work just to ignore this error with —load-error-handling ignore)
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Exception: Qt: Untested Windows version 6.2 detected!
Qt: Could not initialize OLE (error 80070005)
Error: Failed loading page http://xxxxxxxxxx.com/CompanyUsers/Invoices/viewPdf/393 (sometimes it will work just to ignore this error with —load-error-handling ignore)

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

[Exception: Qt: Untested Windows version 6.2 detected!
Qt: Could not initialize OLE (error 80070005)
Error: Failed loading page http://xxxxxxxxxxx.com/CompanyUsers/Invoices/viewPdf/393 (sometimes it will work just to ignore this error with —load-error-handling ignore)
]
Rotativa.WkhtmltopdfDriver.Convert(String wkhtmltopdfPath, String switches, String html) +822
Rotativa.AsPdfResultBase.CallTheDriver(ControllerContext context) +31
Rotativa.AsPdfResultBase.BuildPdf(ControllerContext context) +186
Rotativa.AsPdfResultBase.ExecuteResult(ControllerContext context) +27
System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive(IList 1 filters, Int32 filterIndex, ResultExecutingContext preContext, ControllerContext controllerContext, ActionResult actionResult) +109 System.Web.Mvc.ControllerActionInvoker.InvokeActionResultFilterRecursive(IList 1 filters, Int32 filterIndex, ResultExecutingContext preContext, ControllerContext controllerContext, ActionResult actionResult) +890
System.Web.Mvc.ControllerActionInvoker.InvokeActionResultWithFilters(ControllerContext controllerContext, IList 1 filters, ActionResult actionResult) +97 System.Web.Mvc.Async.<>c__DisplayClass1e. b__1b(IAsyncResult asyncResult) +231 System.Web.Mvc.Controller. b__1d(IAsyncResult asyncResult, ExecuteCoreState innerState) +29 System.Web.Mvc.Async.WrappedAsyncVoid 1.CallEndDelegate(IAsyncResult asyncResult) +111
System.Web.Mvc.Controller.EndExecuteCore(IAsyncResult asyncResult) +53
System.Web.Mvc.Async.WrappedAsyncVoid 1.CallEndDelegate(IAsyncResult asyncResult) +19 System.Web.Mvc.MvcHandler. b__4(IAsyncResult asyncResult, ProcessRequestState innerState) +51 System.Web.Mvc.Async.WrappedAsyncVoid 1.CallEndDelegate(IAsyncResult asyncResult) +111
System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +606
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +288

Читайте также:  What is lubuntu linux

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.17929

The text was updated successfully, but these errors were encountered:

leetruitt commented Oct 15, 2014

I’m seeing this error, too. Have you had any luck tracking down a solution?

I started seeing this after I disabled SSL 3.0 on the server. If I enable SSL 3.0, everything works fine. It’s really strange, but I’ve been able to reproduce it reliably. I’d really like to find another fix, though.

ThatsIT commented Jan 5, 2015

Any news on this I have the same problem also

leetruitt commented Jan 5, 2015

It seems the problem was with wkhtmltopdf. I ended up plugging in a newer version of the executable (wkhtmltopdf.exe) and that fixed my problem. The version I’m using is v0.12.1, which still seems to be the most recent version. You can download that here:

ThatsIT commented Jan 5, 2015

Thanks I was using the nugget package, I had 1.6.1,I updated to 1.6.3-beta than solved my problem
http://www.nuget.org/packages/Rotativa/

AvinashTompe commented Jan 6, 2015

i got the solution for this issue, Rotativa not working when we are using
load balancing, just remove the load balancing of your server.

With Best Regards
Mr. Avinash Tompe
Software Engineer
Cell: 9921323609

On Mon, Jan 5, 2015 at 7:28 PM, ThatsIT notifications@github.com wrote:

Any news on this I have the same problem also

Reply to this email directly or view it on GitHub
#64 (comment).

lkeel75 commented Mar 20, 2015

I was getting the ‘Untested version’ error randomly on my hosted site (hosted by Arvixe). I have been working with them for some time trying to figure out why the functionality randomly works using version 1.6.1. I have a function that prints the same data for a list of students. Sometimes it works and other times calling the same section of code won’t work. I upgraded to 1.6.3 and get a new error every time now. The new error has no message, but does have the same call stack as the ‘Untested version’ error from 1.6.1. The 1.6.3 version works fine if only have 1 student but errors every time if have multiple students. This is the same view & function that randomly works with 1.6.1. Any help suggesting how to resolve or debug this would be greatly appreciated.

webgio commented Mar 20, 2015

@lkeel75 what is the server running on? OS version and IIS version. 32or 64 bit?

lkeel75 commented Mar 20, 2015

This is being hosted by Arvixe so I am going on what they have told me. From what I have gathered: Windows Server 2012 64 bit (confirmed by support team), IIS: Not sure.

lkeel75 commented Mar 20, 2015

I have tried to use the package 1.6.1 and just copied the wkhtmltopdf.exe from the lastest install to the packages folder. But this did not work either.

webgio commented Mar 20, 2015

@lkeel75 you wrote you get no errors? What do you mean? No exception? Also, is this happing on a specific view and other views work?

webgio commented Mar 20, 2015

have you tried 1.6.4-beta?

Il giorno 20/mar/2015, alle ore 17:02, lkeel75 notifications@github.com ha scritto:

I have tried to use the package 1.6.1 and just copied the wkhtmltopdf.exe from the lastest install to the packages folder. But this did not work either.

Читайте также:  Открыть порт линукс firewalld


Reply to this email directly or view it on GitHub #64 (comment).

lkeel75 commented Mar 20, 2015

By no errors I mean that it works. The view that I am creating is being returned as a PDF. I click the same button again to repeat the exact same workflow and I get the error. I have 4 different views that I use the print to pdf functionality on. I get this error randomly on all 4 as well as it randomly works on all 4 views. There is no rhyme or reason as to why it works sometimes and not others. Especially in the cases where 1.6.1 was returning ‘untested os version’.

lkeel75 commented Mar 20, 2015

I have not tried 1.6.4-beta

webgio commented Mar 20, 2015

If you feel to, you can manually replace wkhtmltopdf to the Windows (MinGW-w64) version here: http://wkhtmltopdf.org/downloads.html
I don’t really know the internals of wkhtmltopdf though, it’s just another try you can take. Seems a problem with the server specific setup.
Also, you could try to run wkhtmltopdf from command line, if you have access to it on the server.

lkeel75 commented Mar 20, 2015

I agree on the server setup, but Arvixe is trying to push it to the software (as one would expect). Is the 1.6.4-beta stable? If so, then I will try it. I will also try your other suggestion. THANKS!

webgio commented Mar 20, 2015

I’ll turn it to release soon, I think you can use it, didn’t get any negative feedback.

Il giorno 20/mar/2015, alle ore 17:21, lkeel75 notifications@github.com ha scritto:

I agree on the server setup, but Arvixe is trying to push it to the software (as one would expect). Is the 1.6.4-beta stable? If so, then I will try it. I will also try your other suggestion. THANKS!


Reply to this email directly or view it on GitHub #64 (comment).

serefbilge commented Apr 12, 2015

Hi, I have the same problem. My site is in Arvixe hosting (Windows Server 2012 64 bit) and gave the error below*. Some times it doesn’t give error but it takes long to get result.

And also, I tested the same web project in another server(not a shared one) which of 64 bit Windows Server 2008 R2 Enterprise and IIS 7.5 system and it works fine on this server without error.

Untested windows version detected

I am new to programming using Qt framework

i ran the following example «http://qt-project.org/doc/qt-5.0/desktop-screenshot.html»
Info : Windows 7 64 bit
Qt 5 Beta 2
Qt creator 2.6
Microsoft visual 2010 express
Microsoft Windows SDK v7.1

The compilation was successful and the the program ran as expected, but during subsequent build and runtime the the program hung and screenshot.exe has stopped working window popped up. The application output console in Qt creator displayed

bq. Qt: Untested Windows version 8.3 detected!
C:\Users\abc\Documents\code\screenshot-build-Desktop-Release\release\screenshot.exe exited with code 255

  1. Additional files required to run the screenshot.exe bring up the size of the distribution to 30 MB, while the exe itself is 79 KB in size, i read about static building and couldn’t comprehend the location to set the static flag in Qt creator. Could you please shed come light on it.

A solution to either of the problem, would be appreciated..

If you want to build a Qt application with static Qt libraries, you will have to re-build Qt itself from the sources — as static libraries. The «official» Qt distribution has been built as dynamic libraries (DLL files).

Читайте также:  Резервная копия реестра windows 2003

As for «Untested Windows version 8.3 detected!»: Are you sure the message was exactly like that? The latest version of Windows NT is 6.2 (aka «Windows 8»), the previous version was Windows NT 6.1 (aka «Windows 7»). And yes, Microsoft is really using this illogic version numbering! So there is no such thing as a «Windows 8.3», not even any «Windows 8.x», at present. Which would explain why Qt considers it «untested» when it really came across that version. But the real question is: How can the Windows version be detected as 8.3 .

Its difficult to compile a static version from source, if u can provide a link to static version, it would help to a great extent.

Also i have noticed many of dll added for distribution are not required for the exe to function, is it possible to added flags during compilation to reduce the dependency check to minimum number of dll required for functioning.

The distribution failed to run on XP 32 bit with SP3, no errors were displayed.

Yes, i know the version of windows 7 is 6.1, hence the error has baffled me. I had posted the screenshot as a proof.

Qt will depend on those libraries that you use, most likely you’ll need at least QtCore and QtGui.

Whenever you want to check the dependencies of your EXE file, just use Dependency Walker:
http://www.heise.de/download/dependency-walker.html

Compiling Qt as a static lib really isn’t difficult. Though I have written down some notes here:
http://lamexp.sourceforge.net/doc/FAQ.html#87f001c0

Also I have uploaded my builds here, but currently these are MSVC builds of Qt4 only:
http://tinyurl.com/cn7whoa

Needless to say that there is no guarantee for anything, so better build yourself or use official DLL’s 😉

Thank Mulder for the notes, this simplifies the compilation process.

Any suggestion on the critical error

bq. Qt: Untested Windows version 8.3 detected!
C:\Users\abc\Documents\code\screenshot-build-Desktop-Release\release\screenshot.exe exited with code 255

i am unable to build and run Qt apps

I’m not a Qt developer, so I would suggest to scan the Qt sources (whatever version you are using to build your app) for the string «Untested Windows version», so you can see where exactly that warning is thrown. Then you might be able to track down why it is thrown and where exactly the strange «8.3» comes from.

Thank you, for the advice. Since initially it ran without any hiccup and later builds started throwing this error, i figure its not Qt 5 problem. Anyways will go through the source.

I solved issue, the problem arose when i had added the Qt application(screenshot.exe) in the «Application Verifier» and had closed the app with removing the application from the software. Now i cleared the application using Delete application option in the File tab.

Strange !! this caused such a major issue..

I ran into a similar error when I tried to build a Visual Studio 2010 solution after upgrading to Windows 8.

Qt: Untested Windows version 6.2 detected!
1> Qt User Interface Compiler version 4.7.4
1> Usage: c:\Qt474-msvc2010\bin\uic.exe [options]
1>
1> -h, -help display this help and exit
1> -v, -version display version
1> -d, -dependencies display the dependencies
1> -o place the output into
1> -tr use func() for i18n
1> -p, -no-protection disable header protection
1> -n, -no-implicit-includes disable generation of #include-directives
1> for forms generated by uic3
1> -g change generator
1>
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\Microsoft.CppCommon.targets(151,5): error MSB6006: «cmd.exe» exited with code 1.

The root directory for my solution was C:\Development\PI_Local S23
If I changed it to
C:\Development\PI_Local_S23
The projects would still get the warning but they would build. I’m assuming that the space in the path name made a difference?

Оцените статью