Windows 8 news coverage here


Recommended Posts

Zain Adeel

metro dialogue box :::: YES!! please make aero like that. So that it can all be improved in Win9.

Link to post
Share on other sites
Ben Dyson

Am I the only one that thinks they should use the zune/metro style border for all windows and metrofry all the applications.

You might like looking at clindhartsen portfolio on deviantART, you might also be interested in this concept of a metro explorer.

Link to post
Share on other sites
FaiKee

tweet by Angel of Despair:

image_135.jpg

Google translate :

WZor: Windows 8 Beta has just been signed. The build number will be announced soon

Link to post
Share on other sites
FaiKee

6.2.8175.winmain.111217-1215

image_136.jpg

Google translate :

Last night, ie, December 29, 2011 it became known that the assembly of a candidate in the official beta version of Microsoft Windows 8 Beta was signing and signed (Sign-Off), and so the official beta version will be assembled: 6.2.8175.winmain.111217 -1215

So once December 12, 2011 we reported on the early stage of signing the Microsoft Windows 8 Beta: "the future beta build will be collected up to Christmas ie until December 24, 2011," that we see what happened December 17, 2011 .. .

It is a device (tablet and mobile phones) with this assembly 6.2.8175.winmain.111217-1215 will be holding a Sinovski Steve (Steven Sinofsky) and Steve Ballmer (Steven Ballmer) at Consumer Electronics Show CES 2012 that will take place from 10 to 13 in January 2012.

Microsoft's partners will receive this assembly at the end of January 2012.

Recall that on January 30, 2012 in the Microsoft internal conference is scheduled, ie, the global corporate seating which will debut a wide range of Microsoft employees and partners of the company official beta version of Microsoft Windows 8 beta: 6.2.8175.winmain.111217-1215

At this point, the assembly: 6.2.8175.winmain.111217-1215 is available for a very limited range of workers (engineers, development teams signatories) from Microsoft, each installation of the signed private key for that reason right now, "accidental release" will not, however, We are not sure that this does not happen on 12-14 January 2012

Be patient and wait for Bill Gates is working on it ...

Link to post
Share on other sites
djdanster

6.2.8175.winmain.111217-1215

image_136.jpg

Google translate :

Last night, ie, December 29, 2011 it became known that the assembly of a candidate in the official beta version of Microsoft Windows 8 Beta was signing and signed (Sign-Off), and so the official beta version will be assembled: 6.2.8175.winmain.111217 -1215

So once December 12, 2011 we reported on the early stage of signing the Microsoft Windows 8 Beta: "the future beta build will be collected up to Christmas ie until December 24, 2011," that we see what happened December 17, 2011 .. .

It is a device (tablet and mobile phones) with this assembly 6.2.8175.winmain.111217-1215 will be holding a Sinovski Steve (Steven Sinofsky) and Steve Ballmer (Steven Ballmer) at Consumer Electronics Show CES 2012 that will take place from 10 to 13 in January 2012.

Microsoft's partners will receive this assembly at the end of January 2012.

Recall that on January 30, 2012 in the Microsoft internal conference is scheduled, ie, the global corporate seating which will debut a wide range of Microsoft employees and partners of the company official beta version of Microsoft Windows 8 beta: 6.2.8175.winmain.111217-1215

At this point, the assembly: 6.2.8175.winmain.111217-1215 is available for a very limited range of workers (engineers, development teams signatories) from Microsoft, each installation of the signed private key for that reason right now, "accidental release" will not, however, We are not sure that this does not happen on 12-14 January 2012

Be patient and wait for Bill Gates is working on it ...

What I made from that is no public beta?

Link to post
Share on other sites
FaiKee

What I made from that is no public beta?

According to canouna, build 8175 is quite buggy:

http://forums.mydigitallife.info/threads/30295-News-Discussions-on-Windows-8-Beta-(Sources-WinUnleaked-amp-others)/page81?p=524101&viewfull=1#post524101

Some bugs...

1) Win+R, then type msconfig, go in startup tab, and click on "Open Task Manager" and you get a "Task Manager has stopped working"

2) In IE10, go on youtube, open 3 tabs with a video, get a BSOD.

3) Touch Keyboard is crazy, and if you do a fast typing, he crash.

4) Software issue: just launch cpuZ make crash your OS.

Need to continue?

I guess there is still quite of lot of coding/debugging before it reaches official public beta(build 8200,8300? who knows?). :/

Link to post
Share on other sites
djdanster

Doesn't sound too good now does it :p.

I thought the beta sign off was public beta? Or am I getting confused?

Link to post
Share on other sites
BetaAddict

What I made from that is no public beta?

Yeah, MS is really keeping the builds under lock and key this time around. Public beta is scheduled for sometime in February, so I guess they want to give their partners a first look at it before releasing the same build to the public, barring any major issues.

But damn you MS, why must you make me wait two more months? :pinch:

Link to post
Share on other sites
FaiKee

Doesn't sound too good now does it :p.

I thought the beta sign off was public beta? Or am I getting confused?

It's not the public beta, I am not sure about the "sign-off" meant by WZOR, according to a schedule reported by him earlier (page4,post#54); it marks the accomplishment of a important stage, where a build(8175) is picked from some choices as the candidate for the public beta.

According to a MS China employee, the sign-off of the public beta is expected around mid-Feb, and refering to the WZOR schedule, and also MS has officially announced that the beta release is in late-Feb., don't expect any official release until then.

Rumors were flying around that a leak of 8175 is expected soon, well, rumors are rumors, I am not expecting too much. :D

Link to post
Share on other sites
FaiKee

Yeah, MS is really keeping the builds under lock and key this time around. Public beta is scheduled for sometime in February, so I guess they want to give their partners a first look at it before releasing the same build to the public, barring any major issues.

But damn you MS, why must you make me wait two more months? :pinch:

A few days ago there were rumors that DellChina has the "beta escrow"...well, now it seems it could be the 8175. :rolleyes:

Link to post
Share on other sites
George P

It sounds to me like 8175 isn't going to be the beta, not if it's going to be late in Feb, by then we'll probably be up into the 82xx builds I'd bet.

Link to post
Share on other sites
FaiKee

Seems the MS guys had taken a long holiday, from 8175 of Dec. 17 to 8176 of Jan. 3 :laugh:

image_140.jpg

btw, the build shown in the latest build windows 8 blog was 8165.fbl_fun_resp.111205-2000 - interesting system tray icons.

image_141.jpg

Link to post
Share on other sites
FaiKee

Rumor from win8china:

MS will compile the windows 8 beta escrow on Monday, Jan. 23, 2012 - the date of the Chinese(lunar)New Year.

http://www.win8china.com/html/361.html

We'll just have to wait and see if win8china will be correct this time. :o

Link to post
Share on other sites
George P

Just shows how old 8175 is, Pretty sure they're probably working on 818x builds by today.

Link to post
Share on other sites
FaiKee

Just shows how old 8175 is, Pretty sure they're probably working on 818x builds by today.

:D

image_153.jpg

Link to post
Share on other sites
George P

Wonder what else is new?!?! They really didn't show us anything with 8175 at CES outside of being able to zoom out and in on the start screen using the mouse or the kb.

Link to post
Share on other sites
winrez

^ So we have two Start icons now? :huh:

when you use a touch screen monitor and touch at the right it will bring up the new "charm bar" people that like Windows 7 it will look and act pretty much the same so no worries there.

Link to post
Share on other sites
Crazysah

What is the build number for the upcoming public beta?

Link to post
Share on other sites
George P

What is the build number for the upcoming public beta?

Don't know yet but if they're in the 818x builds now and we know the beta will come in late Feb I guess it's safe to say that 8200 could be the beta build.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By indospot
      Patch Tuesday: Here's what's new for Windows 8.1 and 7 this month
      by João Carrasqueira



      We're 13 days into October, but it's not truly a new month until Microsoft releases its Patch Tuesday updates for Windows, and as we're on the second Tuesday of the month, that happens today. Along with all supported versions of Windows 10, there are also new cumulative updates rolling out to Windows 8.1 and some Windows 7 users.

      There are two kinds of updates for each operating system - the monthly rollup update and the security-only update. For Windows 8.1, the monthly rollup update is KB4580347 and you can download it manually here. It includes the following changes:

      It also has a couple of known issues:

      Symptom Workaround Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following:

      Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.

      When installing a third-party driver, you might receive the error, “Windows can’t verify the publisher of this driver software”. You may also see the error “No signature was present in the subject” when attempting to view the signature properties using Windows Explorer. This issue occurs when an improperly formatted catalog file is identified during validation by Windows. Starting with this release, Windows will require the validity of DER encoded PKCS#7 content in catalog files. Catalogs files must be signed per section 11.6 of describing DER-encoding for SET OF members in X.690.

      If this happens, you should contact the driver vendor or device manufacturer (OEM) and ask them for an updated driver to correct the issue.

      As for the security-only update, it's KB4580358 and you can download it manually here. It only includes the first and last of the bullet points from the monthly rollup. It also has the same known issues as the monthly rollup.

      Of course, for Windows 7, only certain businesses can legitimately obtain the updates, since you need to be paying for extended security updates (ESU) after Microsoft dropped extended support for the operating system at the start of the year. The monthly rollup here is KB4580345, and you can download it manually here. It includes the following changes:

      The update has one known issue:

      Symptom Workaround Certain operations, such as rename, that you perform on files or folders that are on a Cluster Shared Volume (CSV) may fail with the error, “STATUS_BAD_IMPERSONATION_LEVEL (0xC00000A5)”. This occurs when you perform the operation on a CSV owner node from a process that doesn’t have administrator privilege. Do one of the following:

      Perform the operation from a process that has administrator privilege. Perform the operation from a node that doesn’t have CSV ownership. Microsoft is working on a resolution and will provide an update in an upcoming release.

      The security-only update here is KB4580387 and you can get it manually here. It includes the same changes as the monthly rollup, except the third and fourth bullet points. It also has the same known issue.

      As usual, the monthly rollup updates should install automatically sooner or later, but if you want the security-only updates, you'll need to install them manually from the links above.

    • By Usama Jawad96
      Microsoft apparently just fixed a Windows security flaw first reported to it in 2018
      by Usama Jawad

      Microsoft fixed quite a number of bugs in this month's Patch Tuesday update, which came out last week. While it packed numerous fixes for various versions of Windows, it did draw some criticism for the handling of a security vulnerability that was reported to it by Google.

      However, it appears that the Redmond giant's security woes are not yet over as a new report claims that the firm just fixed a Windows zero-day exploit that was reported to it back in 2018.



      Last week, Microsoft fixed a security hole in various versions of Windows that mainly deals with the operating system's incorrect handling of file signatures. In CVE-2020-1464, the company noted that:

      In a blog post on Medium, security researcher Tal Be'ery has explained that Bernardo Quintero, a manager at VirusTotal - a service owned by Google - first discovered the vulnerability being exploited back in August 2018. This exploit, internally called "GlueBall", was immediately reported to Microsoft and the findings were published in January 2019 by Quintero. Microsoft acknowledged the issue and added mitigation actions in supporting tools, but stated that it would not fix the issue in the operating system itself. The reasoning behind this decision is not public.

      After this, several blog posts were published by other people, explaining how to use GlueBall to exploit Windows. Then in June 2020, GlueBall was once again highlighted by prominent social media accounts.

      It would seem that roughly around this time, Microsoft began to take this issue seriously and a proper fix to the gaping security hole was finally released in this month's Patch Tuesday. According to Microsoft's security advisory, this flaw was present in Windows 7, 8, 8.1, RT 8.1, Server 2008, 2012, 2016, 2019, and Windows 10, going all the way up to version 2004, and that it was exploited across numerous versions of the operating system.

      In a vague statement to KrebsonSecurity, Microsoft stated that:

      The handling of this incident from Microsoft's end is extremely strange, to say the least. One has to wonder why Microsoft delayed fixing a Windows security flaw for nearly two years, especially when it was present in virtually all major versions of the operating system.

      Source: Tal Be'ery (Medium) via KrebsonSecurity

    • By Rich Woods
      Microsoft announces Edge is rolling out in the next few weeks, and a bunch of new features
      by Rich Woods



      Microsoft's Build 2020 developer conference starts today, and as always, there's a bunch of news around its brand-new Chromium-based Edge browser. There are a bunch of new features on the way, but perhaps more significant is that the company finally confirmed that it's going to begin rolling out Edge within the next few weeks.

      You might recall that the team actually announced general availability back in January, promising a slow rollout. Slow isn't actually the right word though, because it never actually rolled out. Users have had the opportunity to download a stable version of the browser, and then in February, it started rolling out to beta testers on the Windows Insider Program's Release Preview ring. In other words, other than beta testers, exactly zero people have received this as an update.

      While the blog post doesn't explicitly say this, it seems likely that it's going to arrive as part of the Windows 10 May 2020 Update, which is already available for developers and coming later this month. While the browser is going to be pushed to your machine via Windows Update, updates to the browser will not.

      As mentioned, there are a bunch of new features as well. Collections is getting Pinterest integration, as Microsoft has partnered up with the company. If you're unfamiliar with Collections, it allows you to take images, texts, and links from around the web and store them in groups. Now, you'll see recommendations from Pinterest at the bottom of a Collection. You can also export a Collection to Pinterest. This feature is coming to Edge Insiders within the next month.

      There's also a new sidebar search option coming, so you'll no longer have to open a new tab and lose your focus to search for something on the web. The search results will appear in the sidebar as well. This feature is arriving for Edge Insiders in the coming weeks.

      Edge improvements naturally go hand in hand with Bing improvements. There's a new Work page that's included in Bing search results. It's just another tab along with images, shopping, news, and so on, and it will appear if you're signed in with a work account. The idea is to give Microsoft Search's capabilities to look within your organization its own area, so it will include files, people, internal sites, and so on. Power BI integration is coming by the end of June.

      Finally, Microsoft is releasing a preview of WebView2, which is part of its Project Reunion efforts to unify Win32 and UWP. WebView2 is based on Chromium, so developers can include that in their apps instead of the original EdgeHTML WebView.

    • By Rich Woods
      Microsoft's new Chromium-based Edge browser is now generally available
      by Rich Woods



      It was back in early December 2018 when Microsoft first announced its radical plans to replace its in-house Edge browser with one that's based on Google's open-source Chromium. Today, the new browser is generally available. If you're on Windows 10, you can expect to see it show up on your PC over the next few months if you don't already have it.

      Public testing for the browser didn't arrive until April, and it was only for Windows 10, and only for Canary and Dev channels. Support for Windows 7, Windows 8, Windows 8.1, macOS, Windows Server 2008/2012, and Windows Server 2016+ all came later, as did the Beta channel.

      Obviously, the biggest improvement in the new Edge is that it's based on Chromium, which means that it will render the web in the same way as the most popular browser in the world, Google Chrome. Of course, Microsoft has stripped out all of the Google and added its own bits. It's also contributed quite a bit to the Chromium Project.

      Since it's based on Chromium, you'll actually now be able to use Chrome extensions. Developers can submit their extensions to Microsoft, or you can choose to install them from Google's Chrome Store.

      There are some other new features to call out though. Edge Chromium now has a feature called IE Mode, which will open an Internet Explorer page right within a tab in Edge. It's meant for businesses that have legacy needs, so they'll no longer have to use IE. Of course, IE will continue to ship with Windows 10 for the foreseeable future.

      Another key new feature is called Collections. This allows you to gather up links, images, text, and anything else from around the web and put them into different groups. There are also new privacy features, and a whole lot more.

      Unfortunately, there are a few things that Edge will be missing out of the gate. It won't have native support for ARM64, so if you've got a Windows on ARM PC, you'll have to stick with Edge Canary or Edge Dev for now. Two other things missing will be history syncing and extension syncing. Also, it's not exactly a priority, but the new Edge browser for Xbox One and HoloLens will also be coming later on.

      Again, if you're on Windows 10, you're going to see this show up soon through a Windows update, and it will replace the Edge Legacy browser. If you're on any other supported platform, you'll have to go out and get it. The browser is coming today for Windows 7, which is no longer supported, and while it's unclear how long Edge will remain supported on the legacy OS, Google has committed to another 18 months of full Chrome support.

      If you want to get the new Edge now, you can download the stable version here. As always, you can download a preview version here.

    • By Rich Woods
      Edge Dev build 80.0.328.4 adds a bunch of fixes, but no ARM64 support just yet
      by Rich Woods



      It's a bit late in the week, but Microsoft released a new Edge Dev build today. The build number is 80.0.328.4, and it's a pretty minor update that contains mostly fixes. Yesterday, the Canary channel, which is updated daily, got support for ARM64 PCs, so if you were hoping that this week's Dev build would get the same treatment, you're out of luck. Surface Pro X users will have to wait until next week.

      Here are the changes for better reliability:

      Here are the behavioral changes:

      Finally, there are some known issues to be aware of:

      As you can see, it's quite the changelog, but it's really nothing impactful. Last week at Microsoft's Ignite conference, the company announced that Edge will be generally available beginning on January 15, and that it comes with a new logo.