Tripredacus

I have been sent six Micron SSDs to see if there is any way to save them. They are not covered under warranty and *should* have no data to recover. I have started with one of them, everything seems ok except that anything accessing the disk is very slow, and a partition cannot be created. It appears in Device Manager! It is MICRON_M 510DC_MTFSSAK480 SCSI Disk Device OH, perhaps important information ahead: this disk is in a SATA to USB 3.0 enclosure, connected to USB 3.0 port. Disk Management shows it ok, but there is a red mark on it. Actual size 480 GB seems to be an odd one to me... Crystal Disk Info seems to think everything is fine. Notice the power on count. These disks are not "used" ... and should be "new" but they were found during an acquisition with no asset information. This takes a long time, entire minutes to complete commands such as list disk and sel disk 1 and detail disk, however "clean" seemed to go through quite quickly. Alas, here there is an error trying to create a partition. Here are the things found in Event Viewer: The IO operation at logical block address 0x0 for Disk 1 (PDO name: \Device\00000064) was retried. VDS fails to write boot code on a disk during clean operation. Error code: 800701E3@02070008 The IO operation at logical block address 0x0 for Disk 1 (PDO name: \Device\00000064) failed due to a hardware error. Then I have this from TestDisk running, on partition type "None" and Analyse mode. Seems to be taking its time. If there is any particular tool I can run to get an actual error out of these things, it would be nice. I still have some other things I can try, but being very slow means I have time to post a thread and perhaps go home and take a nap.

I run into many different configurations and only have one process across all images. And that is accomplished by making sure only the disk or vdisk is visible during imaging process. This means not creating or having attached disks or controllers where the OS is not present until after imaging. If a system needs to have a large array built, it is built before imaging and the controller is disconnected until after. A Pro to this is the ability to have one process for tens of different configurations and hundreds of different images. A con is that disk/volume formatting is done manually after imaging process, but before quality phase. This type of process may only work properly in an environment where imaging is done in a specific area, but not work well in corporations that like to do the imaging after physical install in offices, etc. Another way to handle this specific scenario of yours would be to build a custom solution. Where your WinPE would boot to a selection menu of some sort. Present option 1 (1 disk) or option 2 (2+ disks) then execute the appropriate command for each. You would use setup.exe /unattend option and point to either XML file kept in root or wherever. PS: you would get an error if you specify Disk numbers that do not exist.

Add the local account from "This PC" to the share permissions of DESKTOP-ICEONI7. That is the ideal way without enabling guest access on the network. Otherwise, it may be that the new computer has a different network profile set, such as Public instead of Home.

I have installed them onto three computers so far, but have not noticed anything. All three were having issues reading certificates from various things, but the updates did not solve those problems. What are some known situations where you would need these? Are there any websites that are known to require these types of certificates? Something to test against?

There can be various reasons for this, but I would presume that said OEMs are trying to square peg a round hole in their market share. Microsoft makes builds for all sorts of different classes of hardware. If an OEM were to want to create a device that had a small amount of storage, they should be using one of the SKUs specifically designed for such devices, and not be using one of the desktop products. Licensing and product knowledge are things that you would think a company would know, but usually design decisions are not made from the bottom up. Meaning, those who do work with the software and hardware directly are not the ones who would recommend product configurations for their company to sell. The other issue is that most people are willing to just do as directed in order to not cause a fuss or shine a light onto themselves. So bad configurations end up getting into the marketplace because the guy who thought it was dumb just did it anyways. Then, of course, there is the other thing: No one really cares about anything except making a quick buck.

Both methods are doing the same thing. Mine is using AutoIT to read directly from the namespace, while his is reading the output of a WMIC query sent to text file. The registry read doesn't work in Win7 because those keys do not exist. I did a check on my system, and the UUID is not stored in the registry anywhere. There are some situations where you would want to know this information. I personally use it myself for generating hardware specific hashes to things. I do know some other software will use it. Typically you would only need to know it in a situation where a program is not working as desired, which is usually caused by malformed or default UUIDs. Then you would need to know the UUID in order to verify on your own records or to complain to the hardware manufacturer.

Your example is doing the same thing as mine, except using CMD and creating a text file. Mine would only be useful if you wanted to show that data on the Hardware Info MsgBox.

What is the make and model of the board?

I "solved" it by disabling sleep timeout for the monitor. But in reality, it was caused by Windows Update changing the video driver. I remember exactly when it installed that driver because the screen had flickered and it made the connect/disconnect sound. I found in Event Viewer that a new video driver was installed a few minutes prior to that happening.

Looks nice. Some thoughts. 1. Should have some way to differentiate which buttons launch external programs vs which just open a MsgBox. The reasoning is that some things like Device Manager or msinfo32 has some delay in opening. Even something simple like using a Group Control to draw a box around such buttons, or using color coding or highlight. Because (believe it or not) I had not initially thought this program would just open Device Manager when I clicked on that button. 2. AutoIT icon is set for the program. 3. On Windows 7 using the x86.exe, using System Info button, it sees only 2 of my 3 Volumes. Perhaps the same as in your demo screenshot, does it only show the first and last volume? Certainly on the test system you had drive letters in between C and G. And in case you wanted to add UUID functionality, you can refer to this sample: $uuItem = $objWMIService.ExecQuery("SELECT * FROM Win32_ComputerSystemProduct") If IsObj($uuItem) Then For $objSWbemObject IN $uuItem $strIdentifyingNumber = $objSWbemObject.IdentifyingNumber $strName = $objSWbemObject.Name $strVersion = $objSWbemObject.Version Next EndIf $strWMIQuery = ":Win32_ComputerSystemProduct.IdentifyingNumber='" & $strIdentifyingNumber & "',Name='" & $strName & "',Version='" & $strVersion & chr(39) $uiDitem = objGet($sWMIService & $strWMIQuery) If IsObj($uiDitem) Then For $objItem in $uiDitem.Properties_ If $objItem.name = "UUID" Then $itdid = $objItem.value EndIf Next Else MsgBox (0, "Error", "uiDitem is not an object. Content of uiDitem is: " & $uiDitem) EndIf

It says... Version 1809 (OS Build 17763.557).

My Windows 10 Enterprise system has been giving me my first problems so far. Basically is that now when the monitor goes to sleep, the computer makes the disconnecting hardware sound. In addition to that, when I wake the system again, it can take up to three minutes of sitting at the lock screen before it gives me the password prompt. This PC still isn't my daily driver at the office, I only use it for email, intranet and Teams. No surfing, dev work, burning DVDs or using apps or anything.

Fixed the terrible topic title. For the issue at hand, you can parse out the OS name in the filename, but then there are those situations where an update is applicable for an OS that is not in the name. In that case, I am not sure. I have not used Wintoolkit before, when you download from the lists, can you not specify where the files get saved to? Can't have one list go in a folder and another list into another folder?

This appears to be from some German speaking country.

Server edition should see all four cores as four processors. You can forget about workstation. What Service Pack is included on your NT 4 Server media?

The download link indicated via wayback is: http://www.almareader.com/Almareader.exe From here: https://web.archive.org/web/20170722111908/http://www.kolfix.biz/download-ff.html PDF I found relating to it: http://sfile-pull.f-static.com/image/users/233149/ftp/my_files/kolfix and AlmaReader installation and users guide.pdf?id=12302765 The link on this page works to get a version of almareader.exe https://m.tau.ac.il/cc/helpdesk/general/kolfix/kolfix.html

No problem (for me) with the thread, and your account is able to edit that post with no issue.

Win2000Fan is now WinFX.

I'm not sure if this counts as a bug in XP or in Windows 10. The PoC uses schtasks.exe and schedsvc.dll from a Windows XP system on a Windows 10 system. Files from XP work on Windows 10, but when they do, they use priveledge escalation. https://web.archive.org/web/20190522011933/https://github.com/SandboxEscaper/polarbearrepo/tree/master/bearlpe

I think I am just short of 20 years of "IT" experience, mostly due to a couple periods of unemployment and that one year I worked in sales.

Elantec and Synaptics being separate things, always use the one that matches to the Hardware ID of the pointing device in Device Manager. This is important, at least because both companies write their drivers to match on class ids, besides Hardware IDs, meaning you can install the wrong driver without error, but the software won't work.

The ones in the first post and the referenced post work. If you mean something else, link to the specific post. If the content was hosted on another website, be aware of the age of the post.

The host is where the shares are located. The remote or client is the computer attempting to access the shares.

You got me worried, so I had to check on mine, and mine was still set for "let you choose to install them" Things I noticed get reverted: - Sponsored stories for Pocket enabled, although showing Pocket stories on Home page was still disabled. - Do not track was changed to "only known trackers" rather than all sites... I might leave this since "do not track" breaks embedding from many websites. - Location permissions disabled the "block all sites" option (aka doesn't block all sites, only ones in the list already)