Windows 10 News and info | Forum
September 20, 2017, Loading... *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: This is a clean Ad-free Forum and protected by StopForumSpam, Project Honeypot and Botscout | This forum does not use audio ads, popups, or other annoyances.
  Website   Home   Windows 8 Website Windows 8 Forum Help Login Register  
Pages: [1] 2 3 ... 10
 on: Today at 04:27:43 AM 
Started by javajolt - Last post by javajolt
Another day, another Insider build. Just minutes after teasing it on Twitter, the Insider team has released build 16291 to the Windows Insider fast ring, giving us some general tweaks and fixes – as well as one small feature. The build comes as part of a series of small builds that have been rapidly releasing leading up to the full launch of the Windows 10 Fall Creators Update, and its size reflects that. No mobile build is launching with 16291, however.

Here’s the changelog, as seen in Microsoft’s announcement post.

What’s new in Build 16291:

Resume from phones to PC with Cortana: Cortana users can now resume articles, news from their iPhones and Android phones to PC from within the Cortana app. This exciting feature comes in addition to the existing features where users can sync reminders, notifications, and SMS across their devices and stay connected on the go!

General changes, improvements, and fixes for PC:

■ We fixed an issue where sometimes after an upgrade Windows Update’s update history would be missing a listing for the feature update you’d just done.

■ We fixed an issue where scrolling with touch or precision touchpads wasn’t working with the F12 Developer Tools.

■ We fixed an issue where pin reset above lock (“I forgot my PIN”) would only work the first time the password was reset.

■ We fixed an issue where Microsoft Edge would crash if you added a Favorite to a Favorites folder and then immediately sorted that folder by name.

■ We fixed an issue with the indexer from recent flights that could result in Outlook 2016 search failing to index the body of messages.

■ We fixed a recent issue resulting in the Skype UWP app not being launched if it was minimized when you clicked an incoming call notification.

The build should be available right now for those who are a member of the Fast Ring.


 on: September 19, 2017, 09:49:24 PM 
Started by javajolt - Last post by javajolt
Microsoft is today releasing a couple of new things for Windows Insiders today. First up, Redmond is releasing official ISOs for Windows 10 Fall Creators Update build 16278. As per usual, the ISOs are available in the different SKUs and languages, which you can use to either perform a clean install on your device or simply try the build out on a virtual machine. The ISOs can be downloaded here.

Secondly, Microsoft is also releasing the Windows 10 SDK Preview build 16288. The latest build of the Windows 10 SDK doesn’t include any major changes, and it’s likely Microsoft will release the final SDK for the Fall Creators Update sometime very soon. In addition to the new SDK preview, Microsoft is also releasing build 15240 of the Windows 10 Mobile emulator today. You can get them both from the Windows Insider website here.


 on: September 19, 2017, 06:09:12 PM 
Started by javajolt - Last post by javajolt
iOS 11 is scheduled to be released tomorrow (although here's a way you can get your hands on it today if you want), and if you're thinking about upgrading to iOS 11 the moment it's released, there are some steps that you should take so you don't end up in a world of hurt.


The recommended way is to tap Settings > General > Software Update and carry out the refresh from there.

Alternatively, you can connect the iPhone or iPad to a PC running iTunes and do the upgrade from there.


iOS 11 is supported on the following devices:

• iPad Air

• iPad Air 2

• iPad Pro

• iPad mini 2

• iPad mini 3

• iPad mini 4

• iPod touch 6th

• iPhone 5s

• iPhone SE

• iPhone 6/6 Plus

• iPhone 6s/6s Plus

• iPhone 7/7 Plus

This means that not all devices that run iOS 10 can run the iOS 11. Specifically, the following are not supported:

• iPhone 5

• iPhone 5c

• iPad 4

This means that the oldest Apple devices that can support iOS 11 will be the iPhone 5s and iPad Air.


Before you go hog-wild, throw caution to the wind and start upgrading, be aware that there are risks. Things can go wrong, stuff may be broken, and you may lose data. Plenty of iOS launches have been marred by bugs and problems, so with that in mind, it's a good idea to have an up-to-date backup, because making a fuss isn't going to bring back your lost photos or documents.

You can either create a local backup using iTunes, or backup to iCloud by going to Settings > iCloud > Backup, and then turn on iCloud Backup.

Keep in mind that unless you're willing to jump through hoops and do things that Apple frowns upon, going to iOS 11 is a one-way trip, so you might want to let other people to go ahead of you just in case there are gotchas


Chances are that your iPhone or iPad has accumulated a lot of detritus over the months and years, so what better time to get rid of it than now.

While iOS 11 doesn't need as much free space to install as some of the earlier releases of iOS, getting rid of apps that you no longer use -- or perhaps have never used -- makes good sense.


Following the upgrade, you'll need to enter your iCloud password in order to be able to reconnect to all your data and photos. If you don't have this close to hand -- remember, having it on the device you're upgrading isn't all that convenient -- then this might be a good time to do that.

Also, if your iTunes backup is encrypted, then remember you'll need that password if something goes wrong!


The end is nigh for all 32-bit iOS apps, so if you're still relying on older apps, it's time to find alternatives.

For some time now, Apple has been warning iPhone and iPad users that legacy 32-bit apps may slow down their devices, but with the recent release of iOS 10.3, Apple has escalated things by making it clear that the end is nigh.

You can check installed apps for compatibility using the built-in checker tool (you need to be running iOS 10.3 or later for this to work).

You can find that by clicking: Settings > General > About > Applications.

From there, you'll get a list of all the 32-bit apps on your iPhone or iPad that won't run on iOS 11. If you're lucky, you won't have any apps listed, or the apps that are listed will be old stuff that you forgot you had installed and no longer use.

However, if an app that you are relying on is listed, then you need to get ready for its demise.


It's a lot less hassle to just upgrade a device because you get to keep all your apps and settings.

However, devices that I have wiped and reloaded a new iOS onto, and then installed and re-setup all my apps and such, feel faster and seem to suffer from fewer problems (such as Bluetooth and Wi-Fi issues). However, wiping and reloading the apps and data is a pretty big hassle, and it's probably more work than most want to undertake.


There will likely be an update or two to iOS 11 coming down the pipes over the coming weeks, so you might want to wait for the dust to settle and for any last-minute bugs to be squashed before making the leap, especially if you rely on your device.

Also, if you use your device in a BYOD setting, make sure you get the OK from the IT department before upgrading, in case you're unable to access the network or data you need.


 on: September 19, 2017, 02:44:17 PM 
Started by javajolt - Last post by javajolt

You’ve probably seen the posters for the upcoming LEGO movie, this time related to the Ninjago series. To celebrate the LEGO Ninjago film release, LEGO teamed up with Samsung to release a rebranded version of the Galaxy Kids Tab.

This is a rugged machine, meant for the little ones, adorned with LEGO Ninjago pictograms and most likely filled to the brim with related content. There’s the Samsung Kids Suite on board and many games and apps for Ninjago fans. The core device is a Galaxy Kids Tab 7.0 Lego Ninjago Movie Edition, a 7 inch slate with a 1.3 GHz quad core processor, 1 GB of RAM and 8 GB of storage, as well as a microSD card slot.

It also has a 3600 mAh battery and the product is designed for kids who need to keep entertained using such machines. Sadly there’s no info about the availability, but we do know that the device will be priced at $149.99 when it reaches USA later this year. The Samsung Kids service will let parents keep an eye on the little one and how much time he dedicates to the tablet.

Parents can set time limits, select app categories for kids and monitor their progress on a dashboard. No ads are included, so there’s no stress.


 on: September 19, 2017, 02:32:58 PM 
Started by javajolt - Last post by javajolt

There’s such a thing as phones for senior citizens, but what about tablets? Now there’s at least one such model and it’s dubbed the grandPad. This slate is meant for grandparents and it comes just as the population in Western nations is getting older and older. 14% of the world’s population is older than 65 and many people aren’t exactly tech-savvy.

Thus they can have a hard time keeping up with the grandchildren for example. The idea is to offer them an easier way into the technological maze, through intuitive devices. One such product is the grandPad Tablet, designed specifically for seniors with minimal tech skills. This is an 8-inch tablet with 4G LTE connectivity, so there’s no problem if WiFi isn’t available around.

There’s apparently some exclusive thing going on, as the product needs Verizon coverage to work. The tablet uses very simple and intuitive apps to make calls, send emails, play games, check the weather, take and send pictures, or even do video calls. All of that is done without complicated setup, passwords or other distractions. The device can also be set up to view the children or grandchildren pics from Facebook or Instagram.

We don’t have official details, but judging by the device’s screen there’s a 24 Hour Home Care service, that will cater to the elderly and maybe even their potential health needs. An SOS/panic button could also be useful and I’m sure one is here. The grandPad is priced at $75 a month, or you can pay for the full year a one-time $786 fee. This includes the tablet and a free replacement in case of theft or breakage.

More info about the tablet is found here.


 on: September 18, 2017, 11:18:50 PM 
Started by javajolt - Last post by javajolt
Supply chain attacks are a very effective way to distribute malicious software into target organizations. This is because with supply chain attacks, the attackers are relying on the trust relationship between a manufacturer or supplier and a customer. This trust relationship is then abused to attack organizations and individuals and may be performed for a number of different reasons. The Nyetya worm that was released into the wild earlier in 2017 showed just how potent these types of attacks can be. Frequently, as with Nyetya, the initial infection vector can remain elusive for quite some time. Luckily with tools like AMP the additional visibility can usually help direct attention to the initial vector.

Talos recently observed a case where the download servers used by software vendor to distribute a legitimate software package were leveraged to deliver malware to unsuspecting victims. For a period of time, the legitimate signed version of CCleaner 5.33 being distributed by Avast also contained a multi-stage malware payload that rode on top of the installation of CCleaner. CCleaner boasted over 2 billion total downloads by November of 2016 with a growth rate of 5 million additional users per week. Given the potential damage that could be caused by a network of infected computers even a tiny fraction of this size we decided to move quickly. On September 13, 2017 Cisco Talos immediately notified Avast of our findings so that they could initiate appropriate response activities. The following sections will discuss the specific details regarding this attack.

CCleaner is an application that allows users to perform routine maintenance on their systems. It includes functionality such as cleaning of temporary files, analyzing the system to determine ways in which performance can be optimized and provides a more streamlined way to manage installed applications.

Figure 1: Screenshot of CCleaner 5.33

On September 13, 2017 while conducting customer beta testing of our new exploit detection technology, Cisco Talos identified a specific executable which was triggering our advanced malware protection systems. Upon closer inspection, the executable in question was the installer for CCleaner v5.33, which was being delivered to endpoints by the legitimate CCleaner download servers. Talos began initial analysis to determine what was causing this technology to flag CCleaner. We identified that even though the downloaded installation executable was signed using a valid digital signature issued to Piriform, CCleaner was not the only application that came with the download. During the installation of CCleaner 5.33, the 32-bit CCleaner binary that was included also contained a malicious payload that featured a Domain Generation Algorithm (DGA) as well as hardcoded Command and Control (C2) functionality. We confirmed that this malicious version of CCleaner was being hosted directly on CCleaner's download server as recently as September 11, 2017.

In reviewing the Version History page on the CCleaner download site, it appears that the affected version (5.33) was released on August 15, 2017. On September 12, 2017, version 5.34 was released. The version containing the malicious payload (5.33) was being distributed between these dates. This version was signed using a valid certificate that was issued to Piriform Ltd by Symantec and is valid through 10/10/2018. Piriform was the company that Avast recently acquired and was the original company who developed the CCleaner software application.

Figure 2: Digital Signature of CCleaner 5.33

A second sample associated with this threat was discovered. This second sample was also signed using a valid digital certificate, however the signing timestamp was approximately 15 minutes after the initial sample was signed.

The presence of a valid digital signature on the malicious CCleaner binary may be indicative of a larger issue that resulted in portions of the development or signing process being compromised. Ideally this certificate should be revoked and untrusted moving forward. When generating a new cert care must be taken to ensure attackers have no foothold within the environment with which to compromise the new certificate. Only the incident response process can provide details regarding the scope of this issue and how to best address it.

Interestingly the following compilation artifact was found within the CCleaner binary that Talos analyzed:


Given the presence of this compilation artifact as well as the fact that the binary was digitally signed using a valid certificate issued to the software developer, it is likely that an external attacker compromised a portion of their development or build environment and leveraged that access to insert malware into the CCleaner build that was released and hosted by the organization. It is also possible that an insider with access to either the development or build environments within the organization intentionally included the malicious code or could have had an account (or similar) compromised which allowed an attacker to include the code.

It is also important to note that while previous versions of the CCleaner installer are currently still available on the download server, the version containing the malicious payloads has been removed and is no longer available.


Within the 32-bit CCleaner v5.33 binary included with the legitimate CCleaner v5.33 installer, '__scrt_get_dyn_tls_init_callback' was modified to call to the code at CC_InfectionBase(0x0040102C). This was done to redirect code execution flow within the CCleaner binary to the malicious code prior to continuing with the normal CCleaner operations. The code that is called is responsible for decrypting data which contains the two stages of the malicious payload, a PIC (Position Independent Code) PE loader as well as a DLL file that effectively functions as the malware payload. The malware author had tried to reduce the detection of the malicious DLL by ensuring the IMAGE_DOS_HEADER was zeroed out, suggesting this attacker was trying to remain under the radar to normal detection techniques.

The binary then creates an executable heap using HeapCreate(HEAP_CREATE_ENABLE_EXECUTE,0,0). Space is then allocated to this new heap which is where the contents of the decrypted data containing the malware is copied. As the data is copied to the heap, the source data is erased. The PE loader is then called and begins its operation. Once the infection process has been initiated, the binary erases the memory regions that previously contained the PE loader and the DLL file, frees the previously allocated memory, destroys the heap and continues on with normal CCleaner operations.

The PE loader utilizes position independent coding practices in order to locate the DLL file within memory. It then maps the DLL into executable memory, calls the DLLEntryPoint to begin execution of the DLL being loaded and the CCleaner binary continues as normal. Once this occurs the malware begins its full execution, following the process outlined in the following sections.


The DLL file (CBkdr.dll) was modified in an attempt to evade detection and had the IMAGE_DOS_HEADER zeroed out. The DLLEntryPoint creates an execution thread so that control can be returned to the loader. This thread is responsible for calling CCBkdr_GetShellcodeFromC2AndCall. It also sets up a Return Oriented Programming (ROP) chain that is used to deallocate the memory associated with the DLL and exit the thread.

This function is responsible for much of the malicious operations that Talos observed while analyzing this malware. First, it records the current system time on the infected system. It then delays for 601 seconds before continuing operations, likely an attempt to evade automated analysis systems that are configured to execute samples for a predefined period of time or determine whether the malware is being executed in a debugger. In order to implement this delay functionality, the malware calls a function which attempts to ping using a delay_in_seconds timeout set to 601 seconds. It then checks to determine the current system time to see if 600 seconds has elapsed. If that condition is not met, the malware terminates execution while the CCleaner binary continues normal operations. In situations where the malware is unable to execute IcmpCreateFile, it then falls back to using Sleep() to implement the same delay functionality. The malware also compares the current system time to the value stored in the following registry location:


If the value stored in TCID is in the future, the malware will also terminate execution.

Figure 3: Delay Routine

The malware then checks to determine the privileges assigned to the user running on the system. If the current user running the malicious process is not an administrator the malware will terminate execution.

Figure 4: Privilege Check

If the user executing the malware does have administrative privileges on the infected system, SeDebugPrivilege is enabled for the process. The malware then reads the value of 'InstallID' which is stored in the following registry location:


If this value does not exist, the malware creates it using '((rand()*rand() ^ GetTickCount())'.

Once the aforementioned activities have been performed, the malware then begins profiling the system and gathering system information which is later transmitted to the C2 server. System information is stored in the following data structure:

Figure 5: CCBkdr_System_Information Data Structure

Once the system information has been collected, it is encrypted and then encoded using modified Base64. The malware then establishes a Command and Control (C2) channel as described in the following section.


 on: September 18, 2017, 11:18:32 PM 
Started by javajolt - Last post by javajolt

While analyzing this malware, Talos identified what appears to be a software bug present in the malicious code related to the C2 function. The sample that Talos analyzed reads a DGA computed IP address located in the following registry location, but currently does nothing with it:


It is unknown what the purpose of this IP address is at this time, as the malware does not appear to make use of it during subsequent operations. In any event, once the previously mentioned system information has been collected and prepared for transmission to the C2 server, the malware will then attempt to transmit it using an http POST request to 216[.]126[.]225[.]148. The http communications leverage a hardcoded HTTP Host header that is set to speccy[.]piriform[.]com, a legitimate platform which is also created by Piriform for hardware monitoring. This could make dynamic analysis more difficult as the domain would appear to be legitimate and perhaps even expected depending on the victim infrastructure. The requests also leverage http but ignore all security errors as the server currently returns a self-signed SSL certificate that was issued to the subdomain defined in the Host header field. In cases where no response is received from the C2 server, the malware then fails back to a Domain Generation Algorithm (DGA) as described in the section 'Domain Generation Algorithm' of this post.

Once a C2 server has been identified for use by the malware, it then sends the encoded data containing system profile information and stores the C2 IP address in the following registry location:


The malware then stores the value of the current system time plus two days into the following registry location:


Data received from the C2 server is then validated to confirm that the received data is in the correct format for a CCBkdr_ShellCode_Payload structure. An example is shown below:

Figure 6: CCBkdr_ShellCode_Payload Data Structure

The malware then confirms that the value of EncryptedInstallID matches the value that was previously transmitted to the C2 server. It then allocates memory for the final shellcode payload. The payload is then decoded using modified Base64 and stored into the newly allocated memory region. It is then decrypted and called with the addresses of LoadLibraryA and GetProcAddress as parameters. Once the payload has been executed, the memory is deallocated and the following registry value is set to the current system time plus seven days:


The received buffer is then zeroed out and deallocated. The CCBkdr_ShellCode_Payload structure is also deallocated and the malware then continues with normal CCleaner operations. A diagram describing the high-level operation of this malware is below:

Figure 7: Malware Operation Process Flow

Domain Generation Algorithm

In situations where the primary C2 server does not return a response to the HTTP POST request described in the previous section, the malware fails back to using a DGA algorithm. The algorithm used by this malware is time-based and can be calculated using the values of year and month. A list of DGA domains is below:

Figure 8: 12 Month DGA Genearation

The malware will initiate DNS lookups for each domain generated by the DGA algorithm. If the DNS lookup does not result in the return of an IP address, this process will continue. The malware will perform a DNS query of the active DGA domain and expects that two IP addresses will be returned from the name server managing the DGA domain's namespace. The malware will then compute a secondary C2 server by performing a series of bit operations on the returned IP address values and combine them to determine the actual fallback C2 server address to use for subsequent C2 operations. A diagram showing this process is below:

Figure 9: C2 Process Diagram

Cisco Talos observed during analysis that the DGA domains had not been registered, so we registered and sinkholed them to prevent attackers from being able to use them for malicious purposes.


The impact of this attack could be severe given the extremely high number of systems possibly affected. CCleaner claims to have over 2 billion downloads worldwide as of November 2016 and is reportedly adding new users at a rate of 5 million a week.

Figure 10: CCleaner Consumer Demographics

If even a small fraction of those systems were compromised an attacker could use them for any number of malicious purposes. Affected systems need to be restored to a state before August 15, 2017, or reinstalled. Users should also update to the latest available version of CCleaner to avoid infection. At the time of this writing that is version 5.34. It is important to note that according to the CCleaner download page, the free version of CCleaner does not provide automated updates, so this might be a manual process for affected users.

In analyzing DNS-based telemetry data related to this attack, Talos identified a significant number of systems making DNS requests attempting to resolve the domains associated with the aforementioned DGA domains. As these domains have never been registered, it is reasonable to conclude that the only conditions in which systems would be attempting to resolve the IP addresses associated with them is if they had been impacted by this malware. While most of the domains associated with this DGA have little to no request traffic associated with them, the domains related to the months of August and September (which correlates with when this threat was active in the wild) show significantly more activity.

Looking at the DNS related activity observed by Cisco Umbrella for the month of July 2017 (prior to CCleaner 5.33 being released) we observed very little in the way of DNS requests to resolve the IP address for DGA domain associated with this malware:

Figure 11: DNS Activity for July 2017 DGA Domain

As mentioned earlier in this post, the version of CCleaner that included this malware was released on August 15, 2017. The following graph shows a significant increase in the amount of DNS activity associated with the DGA domain used in August 2017:

Figure 12: DNS Activity for August 2017 DGA Domain

Likewise, the DGA domain associated with September 2017 reflects the following activity with regards to attempts to resolve the IP associated with it:

Figure 13: DNS Activity for September 2017 DGA Domain

Note that in on September 1, 2017, it appears that the DNS activity shifted from the DGA domain previously used in August, to the one used in September, which matches the time-based DGA algorithm described in the "Domain Generation Algorithm" section of this blog post. After reaching out to Avast we noted that the server was taken down and became unavailable to already infected systems. As a result, we saw a significant increase in a number of requests that were being directed at the failback DGA domains used by the malware.

Figure 14: Traffic Spike Following Server Takedown

It is also worth noting that at the time of this post, antivirus detection for this threat remains very low (The detections are at 1/64 at the time of this writing).

Figure 14: VirusTotal Detections for CCleaner Binary

As part of our response to this threat, Cisco Talos has released comprehensive coverage to protect customers. Details related to this coverage can be found in the "Coverage" section of this post.

This is a prime example of the extent that attackers are willing to go through in their attempt to distribute malware to organizations and individuals around the world. By exploiting the trust relationship between software vendors and the users of their software, attackers can benefit from users' inherent trust in the files and web servers used to distribute updates. In many organizations data received from commonly, software vendors rarely receive the same level of scrutiny as that which is applied to what is perceived as untrusted sources. Attackers have shown that they are willing to leverage this trust to distribute malware while remaining undetected. Cisco Talos continues to monitor all aspects of the threat landscape to quickly identify new and innovative techniques used by attackers to target organizations and individuals around the world.


The following ClamAV signatures have been released to detect this threat: 6336251, 6336252.

Additional ways our customers can detect and block this threat are listed below.

Advanced Malware Protection (AMP) is ideally suited to prevent the execution of the malware used by these threat actors.

CWS or WSA web scanning prevents access to malicious websites and detects malware used in these attacks.

AMP Threat Grid helps identify malicious binaries and build protection into all Cisco Security products.

Umbrella, our secure internet gateway (SIG), blocks users from connecting to malicious domains, IPs, and URLs, whether users are on or off the corporate network.


File Hashes

DGA Domains

IP Addresses



 on: September 18, 2017, 07:37:41 PM 
Started by javajolt - Last post by javajolt

There are a few companies that have yet to go bezel-free in the smartphone area, even some big names. Sony comes to mind, but also HTC. In the meantime, imagination has already solved that, so we get to see the HTC R-Series, designed by Hasan Kaymak.

This is a massive phablet with a 6-inch screen, with OLED display and dual front camera, something that HTC also hasn’t tried. This is supposed to be an iPhone X rival, plus a Galaxy Note 8 alternative. One of the cams of the dual setup is an ultra wide-angle selfie camera for group photos (12 MP) and the other one is an 18 MP shooter. The back camera is crazy, I mean bananas, with a 42 megapixel Carl Zeiss sensor, that HTC will probably pry from the cold dead hands of HMD Global.

Crazy specs continue with 512 GB of storage and 16 GB of RAM. Wireless charging is also here, being able to charge via pure air, up to 5 meters in distance. This isn’t far off from achieving, but it’s not mainstream yet. The body of the HTC R is made of titanium and I expect this to end up as maybe a Google Pixel 3 phone, especially if Google buys HTC as rumored.

An HTC phone with a glassy body? That’s a rare occurrence… but it may happen.


 on: September 18, 2017, 05:52:00 PM 
Started by javajolt - Last post by javajolt
Microsoft is now adding the finishing touches to its Windows 10 Fall Creators Update OS. As a result, the company is expected to release Windows 10 builds more frequently now.

As a quick reminder, the latest build release is build 16288. However, many Insiders decided to skip this OS version due to the plethora of issues that it triggers. Microsoft already acknowledged the Surface Pro 3 issues on the latest build. Dona Sarkar confirmed that the Insiders Team are investigating the problem and would offer more information on the 16288 issues today.

The good news is that Microsoft is testing a brand-new build internally, and Insiders could get their hands on it today or tomorrow. Of course, the upcoming build should patch all the bugs affecting the current release.

Windows 10 build 16293

The BuildFeed app confirms that the current Windows 10 Fall Creators Update build is 16293, while the current Windows 10 Redstone 4 build is 16366.

Depending on how things evolve with the internal build testing process, the build numbers may change a bit. For example, Fast Ring Insiders could get build 16294 or build 16295 instead of build 16293, but we’re pretty sure that the upcoming build number won’t jump to Windows 10 build 16300 yet.

We’ll keep an eye on the BuildFeed app and update this article as soon as new information is available. Meanwhile, you can still download and test the current Fast Ring build 16288 and the Skip Ahead build 16362.

Speaking of installing Windows 10 builds, we have a question for you: are you planning to install the upcoming Windows 10 build release as soon as it’s available? Or are you going to wait a bit longer to see if Insiders report any severe issues?


 on: September 18, 2017, 05:34:06 PM 
Started by javajolt - Last post by javajolt
Ever since Microsoft pushed out new builds this past week, some users have reported several issues with their Surface Pro 3 devices after the builds are installed. Head of the Windows Insider Program, Dona Sarkar has come out to acknowledge this issue, saying that Microsoft is aware of these problems, and will release more information later today.

An entire thread has surfaced on both Reddit and also the Microsoft Answers forum about the latest issue, with some users reporting that their Surface Pro 3 will no longer boot into Windows after an install of the latest builds. In most cases, it appears Surface Pro 3 devices with build 16288 and 16362 will not move past the boot screen with the spinning dots. Resetting, or using automatic repair will also not resolve the issue.

Since Microsoft originally came across issues with pushing out build 16288, the company may have missed double checking for these issues before re-releasing the build to the public. For now, though, the only way to really resolve these issues is to take the extreme step and reset the Surface Pro 3 to an older production build of Windows 10 using a USB recovery key.


Pages: [1] 2 3 ... 10
Powered by SMF 1.1.21 | SMF © 2017, Simple Machines

Google visited last this page September 19, 2017, 10:55:54 PM