>http://localhost:1169

Same problem if I attempt to install to any where but a virtural directory under default web sites on IIS ie it must be port 80. The wizard in auto will install correctly in this case.

If installing to another port as you are above - the wizard will go into a continous look as you explained - if using auto then it installs but you cannot run it as it keeps looking for the site under localhost not localhost:xxxx even if you edit the portal alais table. So you can never log on. V5 does the same

Just create a virtual directory called DotNetNuke in the default web sites and it should install and run.

Here is my experience... If you are installing and following the guides (create directory, do network permissions, create empty database, edit web.config) - and you are installing a new instance on a system that is not local - the latest 4.9.X and 5.0 hang and never go anywhere.  Installer gets stuck at loading the version tables / stored procedures - and hangs at that point. 

Specifically - what I mean is that the install is on one machine (server) and you are launching the web install from another machine. 

Launch the [hostname]\installer\installwizard.aspx from the server you have IIS configured to host it on and it will go through just fine. 

Another ineteresting behavior is the aborted install.  You have to drop / delete / create empty database and then relaunch the wizard. 

Hopefully that helps as I spent quite a bit of time creating a new website using the newly released bits and totally different behavior than what I saw when I picked up DNN a month or so ago.

Good luck.