/windows | Mar 01, 2017
Well, almost all tiles; the few that remain after running the script below (save as unpin.ps1 then right click and "Run with PowerShell") can be removed manually (right click tile > "Unpin from Start").
/windows | Feb 04, 2017
Received "Failed to write data to disk" error at end of cloning process followed shortly by "Cloning succeeded".
On reboot, the following message appeared:
Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. Insert your Windows installation disc and restart your computer.
2. Choose your language settings, and then click "Next."
3. Click "Repair your computer."
If you do not have this disc, contact your system administrator or computer manufacturer for assistance.
Info: An error occurred while attempting to read the boot configuration data.
Windows booted normally from 4TB SSD.
* IDE/ATA was required in this account, which uses a method similar to Xcopy Windows to a new hard drive, but with ntfsclone (careful with syntax - the target is specified before the source, as explained in the man page:
Clone NTFS on /dev/hda1 to /dev/hdc1:
ntfsclone --overwrite /dev/hdc1 /dev/hda1)
† Destination disk is larger than 2 TB: If "My source disk is MBR and my OS supports UEFI" and "My system is UEFI-booted (Windows or Acronis Bootable Media)" then "partition style on your destination disk will be converted to GPT automatically. This disk may be used for booting in UEFI. Also, the entire disk space will be available."
/windows | Dec 03, 2016
That's it; now you've got a list of all programs easily accessible from the taskbar.
/windows | Oct 11, 2016
:::::::::::::::::::::::::::::::::::::::::::: :: Automatically check & get admin rights V2 :::::::::::::::::::::::::::::::::::::::::::: @echo off CLS ECHO. ECHO ============================= ECHO Running Admin shell ECHO ============================= :init setlocal DisableDelayedExpansion set "batchPath=%~0" for %%k in (%0) do set batchName=%%~nk set "vbsGetPrivileges=%temp%\OEgetPriv_%batchName%.vbs" setlocal EnableDelayedExpansion :checkPrivileges NET FILE 1>NUL 2>NUL if '%errorlevel%' == '0' ( goto gotPrivileges ) else ( goto getPrivileges ) :getPrivileges if '%1'=='ELEV' (echo ELEV & shift /1 & goto gotPrivileges) ECHO. ECHO ************************************** ECHO Invoking UAC for Privilege Escalation ECHO ************************************** ECHO Set UAC = CreateObject^("Shell.Application"^) > "%vbsGetPrivileges%" ECHO args = "ELEV " >> "%vbsGetPrivileges%" ECHO For Each strArg in WScript.Arguments >> "%vbsGetPrivileges%" ECHO args = args ^& strArg ^& " " >> "%vbsGetPrivileges%" ECHO Next >> "%vbsGetPrivileges%" ECHO UAC.ShellExecute "!batchPath!", args, "", "runas", 1 >> "%vbsGetPrivileges%" "%SystemRoot%\System32\WScript.exe" "%vbsGetPrivileges%" %* exit /B :gotPrivileges setlocal & pushd . cd /d %~dp0 if '%1'=='ELEV' (del "%vbsGetPrivileges%" 1>nul 2>nul & shift /1) :::::::::::::::::::::::::::: ::START :::::::::::::::::::::::::::: REM Run shell as admin (example) - put here code as you like ECHO %batchName% Arguments: %1 %2 %3 %4 %5 %6 %7 %8 %9 cmd /k
/windows | Sep 04, 2016
Boot via Windows installation media (DVD, USB flash drive, etc)
When the "Windows Setup" window appears, press Shift + F10 to open a command prompt
Launch one of these tools from the command prompt to retrieve product key from BIOS / UEFI:
Windows OEM Product Key Tool 1.1 - Purpose-built app; simply returns the product key
FirmwareTablesView - Displays list of firmware tables; look for "MSDM" under Signature column or "Microsoft Software Licensing Table" under Description column
RWEverything - Digs deep for a plethora of hardware details; head to ACPI > MSDM > Data.
To identify which version of Windows the recovered product key corresponds to:
Ultimate PID Checker - Works with product keys from XP through 8 (not 8.1); runs inside the Windows installation environment
ShowKeyPlus - Works with product keys from Windows 7 through 10; does not run inside the Windows installation environment
For OEM computers still shipping with Windows 7 or 8.1 (slated to end on October 31, 2016), the firmware-embedded product key likely differs from the product key on the hard drive. Recover the latter with ProduKey.
For more information on embedded product keys, see Windows 10 Embedded Product Key Tool and Where is my Windows product key, and how can I tell that my Windows installation is genuine?
/windows | Sep 04, 2016
/windows | Sep 04, 2016
While attempting to install Windows 7 on a Dell Optiplex 3040 Micro, the following error appeared:
A required CD/DVD drive device driver is missing. If you have a driver floppy disk, CD, DVD, or USB flash drive, please insert it now.
Note: If the Windows installation media is in the CD/DVD drive, you can safely remove it for this step.
Browse | OK | Cancel
(As it turns out, the problem is caused by a missing USB 3.0 driver, so installing via USB floppy, CD/DVD, flash drive, etc was not possible.)
Browsing for a driver on the virtual X: drive returned:
No device drivers were found. Make sure that the installation media contains the correct drivers, and then click OK.
Reports online did not sound promising, e.g.: 'No device drivers were found' error when installing windows 7 on new computer "FINAL EDIT - If you're here for answers, while nothing here worked for me, that doesn't mean it won't work for you, so I suggest you try everything here if you can. What I ended up doing is giving up on windows 7 and instead installed windows 10.").
Coming up with a working solution took more time than anyone else should ever have to invest in this issue again. Here's what worked for me:
Format a USB drive as NTFS. If necessary, use diskpart.exe:
select disk x, where x is the number assigned to your USB drive
create partition primary
select partition 1
format fs=ntfs quick
Copy files and folders from Windows 7 ISO or DVD to USB drive
Download Intel(R) USB 3.0 eXtensible Host Controller Driver and extract contents
Download, install, and run NTLite
Click "Add" > "Image folder" > select drive letter of USB drive (E: in the example that follows) > click "Select Folder"
Under "Operating systems | install.wim", right click the version of Windows that corresponds to your license and then click "Load":
Once loading has completed, click "Drivers" in the left-hand column:
Click "Add" > "Folder with multiple drivers" > browse to the folder containing extracted driver(s) > click "Select Folder"
Click "Apply" in left-hand column > click green "Process" button at top left > "Yes"
When processing is complete, click "Source" in the left-hand column to return to the main window
Repeat steps 6 through 10 for the two entries under "Boot/Setup | boot.wim" (in the screenshots above, they are "Microsoft Windows PE (x86)" and "Windows 7 Setup")
If desired, make an ISO image of the USB drive (for burning to DVD-R, etc) by right clicking E: under "Image history" and then clicking "Create ISO"
The USB drive or ISO image can now be used to install Windows 7 on the affected computer (see below for a list of all affected Dell models)
Dell explains the cause here: Dell systems with the Intel Skylake or Braswell Chipset cannot boot to Dell Windows 7 media due to no USB 2.0 but the NTLite directions are incomplete (as of August 21, 2016) to the point of being virtually useless. In an update to their post, Dell recommends using instead:
Intel's Windows 7 USB 3.0 Creator Utility ("This utility automates the process to create a Windows 7 installation image to include USB 3.0 drivers. The new installation image can then be used to install Windows 7 on Intel® NUC products that have only USB 3.0 ports."). However, it would crash towards the end of the process and the image it created did not include the necessary USB 3.0 driver. Also, it only runs under Windows 8.1 or higher (?!) and (according to the instructions) requires Windows USB/DVD Download Tool (which Microsoft inexplicably hosts at http://wudt.codeplex.com/ and last updated in 2009), which requires Microsoft .NET Framework v2 and Microsoft Image Mastering API v2! Since v2 does not run under Windows 8.1, 3.5 was tried, but ultimately the Download Tool did not work out (nor did Rufus), though this could have been caused by running in a virtual machine (which worked fine for the process outlined above).
Fiddling with the scant USB and virtualization options in the BIOS did not avail.
Old timers will note the similarity between this issue and the Windows XP / SATA install problem from yesteryear.
Before piecing together the above procedure, used this old workaround:
Remove SATA HDD from Optiplex 3040 and install into generic PC.
Install Windows 7 normally
Shutdown at initial welcome screen (Shift+F10,
shutdown -t 1 -s)
Boot generic PC once more from Windows 7 installer and use regedit to switch from IDE to AHCI mode if necessary:
Shift+F10 > regedit.exe
Load \windows\system32\config\system (which corresponds to HKEY_LOCAL_MACHINE\SYSTEM\)
Navigate to ControlSet001\services\msahci and change "Start" DWORD value from 3 to 0.
Repeat step c for ControlSet002\services\msahci
Copy missing drivers to SATA HDD
Reinstall SATA HDD into Optiplex 3040 - Windows boots normally. Install missing drivers.
Here is the current list of affected Dell computers: Latitude E7270, Latitude E7470, Latitude 3470, Latitude 3570, Latitude E5270, Latitude E5470, Latitude E5570, Latitude 7370, Latitude 7414 Rugged, Latitude 7214 Rugged, Latitude 5414 Rugged, Optiplex 7440 AIO, Optiplex 3240 AIO, Optiplex 7040, Optiplex 5040, Optiplex 3040, Precision Tower 3620, Precision Tower 3420, Precision MPWS 7510, Precision MPWS 7710, Precision MPWS 3510, XPS 9550, XPS XPS 13 9350, XPS 8900, Inspiron NB 7559, Inspiron NB 3452/3552, Inspiron NB 3459/3559, Vostro NB 5459, Inspiron DT 3059, Inspiron DT 3459, Inspiron DT 5459, Inspiron DT 3650, Inspiron DT 3250, Vostro DT 3650, Vostro DT 3653, Vostro DT 3250, Vostro DT 5450
Latest Intel, AMD chips will only run Windows 10 ... and Linux, BSD, OS X - "One example of Microsoft holding back support is the xHCI USB controller in sixth-generation Skylake and seventh-generation Kaby Lake: Windows 7 doesn't support that USB hardware, so installing the operating system from a USB stick using those chips is tricky. Intel provides xHCI drivers for Windows 7 once it's up and running."
Microsoft made 'em do it: The latest Kaby Lake, Zen chips will support only Windows 10 - ". . . the company tried to shorten its support lifecycle for Intel Skylake PCs running Windows 7 and 8, a policy the company subsequently abandoned after much outcry. But Microsoft's statements have also consistently included a critical caveat: The latest generations of silicon—specifically Intel's Kaby Lake chip, Qualcomm’s 8996, and AMD’s Bristol Ridge silicon—will all require Windows 10.
Microsoft Suspends Win 7/8.1 Updates For Intel Kaby Lake, AMD Ryzen CPUs - "Microsoft suspended updates for Windows 7 and Windows 8.1 users with Intel's 7th generation (Kaby Lake) processors, AMD's 7th generation (Bristol Ridge) processors, and Qualcomm's 8996 processor or newer. The company said before that it wouldn't release new drivers for older Windows versions to support new hardware, but now it's stopped Windows 7 and Windows 8.1 users with these new CPUs from scanning or downloading from Windows Update."
/windows | Aug 21, 2016
/windows | Jul 09, 2016
PatternName PatternMatch ----------- ------------ Gmail &Emailemail@example.com&Passwd=PASSWORD_IN_PLAINTEXT&Persiste...
mimikittenz currently extracts the following credentials from memory:
/windows | Jul 08, 2016
Subscribe or visit the archives